
Systemic methods for collaboration
Why do well-intentioned impulses in a team so often fizzle out? Systemic consulting explains how connectivity determines impact.
Conversations with testers, developers, and coaches who work in the field.

Why do well-intentioned impulses in a team so often fizzle out? Systemic consulting explains how connectivity determines impact.

Testing AI sounds complex but often boils down to one question: deterministic or not? What that means for your whole test strategy now.

Agile transformation with a hangover? Four change models show why change fails and how small steps achieve more than major upheavals.

AI testing, test data, accessibility: which trends testers should really have on their radar and why the right tool often doesn't solve the actual problem.

AI doesn't make developers more productive, it makes them faster at creating legacy code. What this means for quality and jobs until 2034.

From July 2025, penalties of up to 100,000 euros apply for missing accessibility. What that means for design, development and for testing.

Software testing often shows a gap between theory and daily practice in projects. AI-supported certification aims to close exactly that.

A 97 percent reduction in image file size through just three adjustments. How performance thinking makes sustainable software practical.

LLMs testing like a pro: Acceptance Test Driven Development meets fine-tuning - creating a measurable quality process for AI systems.

Without a test structure, without a budget, without ready-made tools: How one team built real quality assurance step by step.

A test automation monolith that has grown for years, XML everywhere in the code like a tumor: How to refactor anyway and what really counts.

Stoic principles in product management: Those who judge decisions by the result make the wrong judgment. Three lessons that change that.

Lots of unit tests, high test coverage, but still bugs. Why the test pyramid is often used incorrectly and when other approaches make more sense.

Separating functional and quality requirements: useful or misleading? What this distinction really means for architecture decisions.

Anyone who plans acceptance testing shortly before delivery is testing quality at the most expensive time. What early integration really brings.

Test strategy via workshop instead of a hundred-page document: How a collaborative format quickly brings teams to a common test picture.

Why should the earth be a stakeholder in the next sprint? Sustainable software saves costs, conserves resources and makes systems better for everyone.

Since 2011, the German Testing Day has combined practical experience, an independent board and unusual keynotes - what sets this conference apart from the rest.