
Transition to open source test automation
A test automation monolith that has grown for years, XML everywhere in the code like a tumor: How to refactor anyway and what really counts.

A test automation monolith that has grown for years, XML everywhere in the code like a tumor: How to refactor anyway and what really counts.

Stoic principles in product management: Those who judge decisions by the result make the wrong judgment. Three lessons that change that.

Lots of unit tests, high test coverage, but still bugs. Why the test pyramid is often used incorrectly and when other approaches make more sense.

Separating functional and quality requirements: useful or misleading? What this distinction really means for architecture decisions.

Anyone who plans acceptance testing shortly before delivery is testing quality at the most expensive time. What early integration really brings.

Test strategy via workshop instead of a hundred-page document: How a collaborative format quickly brings teams to a common test picture.

Why should the earth be a stakeholder in the next sprint? Sustainable software saves costs, conserves resources and makes systems better for everyone.

Since 2011, the German Testing Day has combined practical experience, an independent board and unusual keynotes - what sets this conference apart from the rest.

Software acceptance usually checks functions only and nothing beyond that narrow scope. Whether up to 12,000 hidden bugs count as normal.

Conflicts in a team are not a disruption - they are energy. How to recognize them early, address them correctly and use them for the team.

One year, 67 episodes, over 22,000 downloads: What became of a spontaneous video idea and where the journey will take us next.

Scrum provides a process, but not a plan for good requirements. What happens before the backlog often determines product success more than any sprint.

Choosing an E2E test automation framework starts with the requirements, not with the tool. That saves the expensive framework switch later.

Quality remains invisible, no matter how much you invest. Why testing is nevertheless becoming more important and which two steps count now.

Remote teams can work better together than office teams, but only on one condition: Knowledge must be networked, not people.

From the I-Shape to the V-Shape: Why testers will need in-depth knowledge in several areas in the future and how cell teams could replace hierarchies.

Five tools, manual transfer errors and no cross-system solution: that was test data management. A store concept changed the entire setup.

Using ChatGPT for test cases, test data and exploratory ideas: What really works, where caution is advised and why prompting matters.