
Sustainability
Sustainability in software development has seven dimensions and most know only one. What carbon footprint, use and green features mean.
Conversations with testers, developers, and coaches who work in the field.

Sustainability in software development has seven dimensions and most know only one. What carbon footprint, use and green features mean.

outsourced in 1978, paid according to test cases and errors found: Why this approach failed back then and which principles still apply today.

Meetings where everyone nods and nobody really thinks can be designed differently. Liberating Structures provides the concrete formats.

Model-based testing is considered complex and formal. Boxes, arrows and a flowchart are enough to uncover requirement gaps early on and generate test cases.

Cloud migration sounds like technology but is largely a question of organization instead. Monoliths, DBAs and silos slow things down most.

Finding 80% of errors in 1% of the time: How test impact analysis and test gap analysis are fundamentally changing testing.

BDD looks simple, but it's not. Why Gherkin without real team communication creates more effort than benefit, and how to do it right.

Two years of work, an international team, a completely revised basis: what has really changed in ISTQB Foundation Level 4.0.

Why are hundreds of unit testers created, but the software still doesn't run? Because isolated tests alone do not prove a feature - and that is the problem.

Manual testing is no fun, and risk analyses usually end up unread in a drawer somewhere. Gamification solves both with concrete formats.

70.000 copies sold, but testing is still considered destructive. Why this image is wrong and what it really means to test software.

C++ is 45 years old and yet deeply rooted in autonomous driving, medical devices and AI libraries. What the Core Guidelines have to do with it.

How do you test an app that drivers use while driving without distracting them? Test drives, surveys and slow rollouts on 20% of the fleet.

Agile quality needs more than test automation: roles, approach and processes must fit together. The House of Agile Quality shows you where to start.

If you only check quality during testing, you've already lost. How unit tests, IDE plugins and contract testers make errors visible earlier.

Four to six people, one keyboard, real code: Ensemble Testing brings testers and developers together where documentation and meetings fail.

Cypress instead of Selenium: Why real browser testing is more stable, how component testing saves the test pyramid and where the tool's limits lie.

Testing audio AI without being able to look into the code: Why golden test sets, training data tracking and ChatGPT play a role in this.