
From the test factory to QA coaching
Eight people, 100 applications, a test manual that nobody read: How a QA team ditched the control function and replaced it with coaching.
Conversations with testers, developers, and coaches who work in the field.

Eight people, 100 applications, a test manual that nobody read: How a QA team ditched the control function and replaced it with coaching.

85 percent of cyberattacks start with a human error. How nudging leads users to safe behavior without forcing them.

Nonviolent communication has four components: Observation, feeling, need, request. What this looks like in everyday testing.

Insurance salespeople test releases themselves when tools and coaching are right. A Center of Excellence needs three minutes per release.

If you calculate target values for 2,500 signals manually, you lose the connection. How a reference implementation as a test oracle solves this.

If you really want to understand agile working, you don't need a slide - you need a board, cards and a round of simulation.

Test plans that end up in a drawer don't help anyone. How a modular QA toolkit is changing that and why it will soon be open source.

End-to-end across web, desktop, database and 3270 hosts: where Robot Framework earns its place, where web-only tools stop, and why it won't die soon.

Why do most podcasts die after seven episodes? Continuity beats perfection - and how conferences become a topic turbo.

Anyone who configures SAP is really testing side effects across the whole system. Why enterprise testing needs its own rules and skills.

From a sluggish monolith with hours of end-to-end testing to fast microservices: Which test strategy really works for this.

Informal networks are who people actually turn to when things go wrong. Why they decide how fast teams adapt, and why you cannot order them into being.

Testing AI without structure is like testing without scale. How a three-dimensional matrix brings order to the chaos of AI testing dimensions.

Quality responsibility does not end at the story boundary. How quality coaching in SAFe closes the gaps between teams that nobody wanted to see.

Migrating from Cypress to Playwright took one team over a year next to daily QA work. The stumbling blocks: session handling, request interception, grown tests.

Which headline do you not want in tomorrow's paper? Risk-based testing starts with that question. One team cut its end-to-end tests by 50 to 60 percent.

280 UI tests in under three minutes without a backend are possible with isolated UI testing. Mocked API responses keep the suite stable.

Requirements often have more gaps than expected, and DEFOSPAM uncovers them systematically. AI can support exactly this analysis step well.