
Why AI cannot do cause-and-effect - and QFD helps
Why can't LLMs do cause-and-effect? And what does Quality Function Deployment have to do with it? The answer changes how you prioritize testing.
Conversations with testers, developers, and coaches who work in the field.

Why can't LLMs do cause-and-effect? And what does Quality Function Deployment have to do with it? The answer changes how you prioritize testing.

Standards do not make secure software by themselves - but 62443-4-1 shows how security really belongs in the process from the very first design step.

From developer to test automation engineer: Why clean code principles decide which automation lasts for years and which doesn't.

A product test runs long before the magazine appears, with independent purchase and blind tests. Multiple checks mirror software testing.

130 participants, a clear focus on test automation and real practical reports: Why TACON in Leipzig attracts more and more people every year.

60 to 80 participants, no fixed schedule and still the most intensive technical talks. What a barcamp does differently from a conference.

Test reporting in 5 steps: Goal, position, forecast, data quality and automation. How reporting becomes a real management tool.

Formal methods sound like an ivory tower, but they provide what testing alone can never do: mathematical proof of correct behavior.

527 submissions, just under 50 slots: How a conference program is really created and what makes one submission stand out from the rest.

AI-generated test cases in the medical technology environment: how a RAG system remains regulatory clean without tool validation.

600 production runs, one workflow, not a single test for it: How process mining shows what regression testing really needs to cover.

AI-generated code sounds tempting, but who pays the bill? Why software engineering needs more quality control, not less.

Quality in start-ups is not created by processes, but by attitude. Why testers need to be louder than developers.

Specialist departments hardly test at all because test knowledge is missing in the teams. An AI assistant delivers cases to ISO standards.

Two years of exploratory ensemble testing in a real project: What the method brings, where it gets stuck and why testing is suddenly fun.

Error culture sounds good on the vision board, but collapses at the first real bug. What really helps before the stress comes.

200 system states and a virtual control unit replace the physical test cabinet in e-cars. Thermal management tests get earlier and sharper.

176 episodes, 122,000 downloads, flaky tests, AI fears and a microphone faux pas: what the year really left behind.