
Test description for AI capabilities
Making AI systems testable: How capabilities, quality criteria and structured test descriptions turn abstract standards into concrete testing approaches.
Conversations with testers, developers, and coaches who work in the field.

Making AI systems testable: How capabilities, quality criteria and structured test descriptions turn abstract standards into concrete testing approaches.

Only 6% of surveyed testers fit the IT stereotype, the rest come from other fields. Why HR departments should sit up and take notice of this.

Many people know test design methods, but hardly anyone uses them. Why this is the case and how AI closes this gap without making you stop thinking.

Those who test protect everyone on the team and in the project, not just themselves. A test net for embedded builds on CMake and Google Test.

Every mutant reruns your test suite, and that gets slow fast. How incremental analysis in PIT and a focus on core logic make mutation testing pay off.

25 to 30 test design techniques exist, five cover most cases in practice. How to pick the right one by problem type, risk level and team skills.

Why does your brain just not understand some code? Working memory only processes four chunks at a time, and good code respects this limit.

700.000 lines of code in a combi steamer, 2,000 test cases per night: how test automation really works in device development.

Who is really responsible for quality in a company often remains unclear. The ACT2LEAD model shows what leadership in testing actually looks like.

Why do some teams feel great after shared work - and others wear down? What separates smart organizations from dumb ones.

AI is becoming the standard tool in testing, accessibility is becoming mandatory and test automation continues to gain momentum. What really matters in 2025.

AI dominates programming and testing, but lags behind in requirements engineering. Where Scrum really stands today and what that means for software quality.

Accessibility does not work automatically just because components are accessible. What goes wrong when assembling and why manual testing remains.

What happens when a third of the adopted code is only available as a black box? How an agile mindset and honesty can save a ticket store project.

Anyone familiar with impostor syndrome knows that rational thinking often doesn't help. Which strategies really lead out of the impostor cycle.

Model-based testing sounds good but often fails on the gap between model and actual test. A two-phase approach closes exactly that gap.

AI-generated test code compiles cleanly but very often tests the wrong thing entirely. Writing unit tests yourself is the smarter route.

Type systems, Windows drivers, payment rollbacks, the seL4 kernel: where formal methods run in practice, and why a proof can cost ten lines per line of code.