Effective test reporting without overhead
Test reporting in 5 steps: Goal, position, forecast, data quality and automation. How reporting becomes a real management tool.
Conversations with testers, developers, and coaches who work in the field.
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 ever test because there is a lack of test knowledge. How an AI assistant called Sherlock is changing this and delivering test cases according 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 possible system states, a virtual control unit instead of a physical test cabinet: how thermal management tests in electric cars are becoming earlier and more precise.
176 episodes, 122,000 downloads, flaky tests, AI fears and a microphone faux pas: what the year really left behind.
AI doesn't make bad processes better, it catches up with them faster. What testers really need in 2026: Gut feeling, basic knowledge and community.
Autism in software testing: Why an autistic brain finds bugs instead of looking for them, and what teams can learn from it.
Let API interfaces continue to break silently or recognize them early? Contract testing shows how consumers specify what they need and changes stop the pipeline.
From two weeks of manual testing to three hours: how an AI-based solution automates legacy apps without element IDs.
Errors usually occur long before anyone tests. Quality Storming makes visible where quality is lost in the process - before it's too late.
164 subsystems, lightning protection according to national law, offshore turbines without service access: testing software in wind turbines is more complex than it seems.