
Green software revolution
Sustainability has long been part of ISO 25010, only hidden between quality criteria. How testers work more resource-efficiently today.
Conversations with testers, developers, and coaches who work in the field.

Sustainability has long been part of ISO 25010, only hidden between quality criteria. How testers work more resource-efficiently today.

User stories should be testable, everyone nods and hardly anyone knows how it works. What requirements engineering adds and which tests help.

Accessibility in mobile testing: Why assistance systems hinder each other and which test matrix helps.

Rather than testing for errors, Quality by Design avoids introducing them at all. The approach comes straight from the pharma industry.

Teaching quality as a compulsory subject is not enough. How measurement, resource thinking and sustainability are becoming part of everyday life at university.

Agile testing has long been common sense, but why does overall quality still fail when twelve teams run at each other?

60 teams, 15 quality specialists: How quality remains anchored everywhere when coaching becomes more important than classic testing.

6.000 test cases, CI runtime under 10 minutes: How test-based selection via code coverage makes exactly that possible.

57 percent of accessibility criteria can be tested automatically - the rest requires human judgment and the right process.

Teams often make architecture decisions unconsciously while coding. Three experiments show how this can be achieved jointly and comprehensibly.

Demanding maintainability early while the market is still missing is wrongly prioritized. The evolution model shows which quality goals count.

In automotive testing a windshield wiper already counts as a safety-critical system. What that means for test methods and for standards.

Out of 73 universities audited, they had to abandon one in five because there were too many gaps. What this means for software security.

Shift left sounds good, but does it really make a difference? How six years of data show what Continuous Everything actually changes and what it doesn't.

Throwing specifications over the fence belongs to the past in modern software projects. Domain storytelling unites users and developers.

Coaching and software testing share far more than most people expect in daily work. Clarifying orders and spotting patterns are real levers.

Good team goals don't fail because of the concept, but because they disappear in everyday life. Three to five metrics and a moderator change that.

Change does not fail because of the idea, it fails because of the process around it. Why skeptics are allies and emotion beats slide decks.