Test pyramid - a critical look
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.
Conversations with testers, developers, and coaches who work in the field.
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.
Those who accept software usually only test functions. Whether up to 12,000 undiscovered bugs are normal and what "state of the art" really means in legal terms.
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.
Which E2E framework really suits your project? If you clarify the requirements first, you'll make the better choice - and save yourself the expensive switch afterwards.
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 different tools, manual errors when transferring, no cross-system solution: this is what test data management looked like in practice before a store concept changed everything.
Using ChatGPT for test cases, test data and exploratory ideas: What really works, where caution is advised and why prompting matters.
Zero Trust is more than just a buzzword: if you don't define it yourself, you're talking past each other. What it means in concrete terms and where to start.
Testing AI means rethinking: no clear test oracle, statistical quality instead of pass/fail. What this means in concrete terms and which methods really help.