
World Quality Day
What does quality actually mean when no one in the team has an answer? A look back at 20 years of testing and the questions that are now becoming urgent.
Conversations with testers, developers, and coaches who work in the field.

What does quality actually mean when no one in the team has an answer? A look back at 20 years of testing and the questions that are now becoming urgent.

Shift left parallelizes testing before go-live, shift right watches production. One insurer runs the same UI tests in both worlds. How that works.

Production data often only covers 70% of test cases. How to systematically test data processes and get business and IT on the same page.

More data does not automatically mean better decisions. Which software metrics really help and why context is more important than any number.

Anyone who writes requirements already thinks like a tester - or should. A look at a data warehouse project shows how this ensures quality at an early stage.

From tester to leader: Why the interpersonal challenges exceed anything a leadership course can ever prepare.

Pen tests at the end of a project always find the same headers, misconfigurations and gaps. Security in the pipeline cuts that to a handful.

The hardware arrives late, testing starts anyway. Why simulators fail at timing and bus protocols, and when real target hardware belongs in the CI pipeline.

255 form variants, 16 federal states and over 100 fields per form stay manageable. Model-based test data and generic UI automation help.

Mechanical engineers and the Cyber Resilience Act: What companies can expect, where the real hurdles lie and why early action brings a concrete cost advantage.

Testing is a team affair, not a lone wolf discipline. Which skills are really in demand today and how to plan your career path in testing.

Architecture documentation quickly becomes outdated because the tools slow it down. Documentation as Code and Continuous Documentation solve exactly that.

Security is often the last item on the agenda - and that is precisely the problem. What defense in depth, threat modeling and secure defaults really mean.

The Software Testing Survey has been running every few years since 2011, now for the fourth time. What has really changed in testing since then.

90% of failed tests are real bugs, not automation errors. Why no project can do without manual testing.

Quality coaching differs from traditional consulting: solutions are created in the team, not in front of it. Which methods make this possible.

Why security in the development team hardly gets through despite a high level of awareness, and which approach really works in practice.

Accessibility tests today end up in a jumble of Word, Excel and browser tabs. How an integrated test environment can change this and how AI can help.