Test Quality – Craftsmanship for Testers

Quality is not a phase

Many teams do a lot of testing, but without a clear strategy behind those choices. Risks remain implicit, test suites become fragile, integration issues surface late, and quality remains something owned by the QA department instead of the whole team.

In this training, you’ll learn how to approach this systematically. Not with a checklist, but with a coherent view of what good testing means: context over dogma, risk over percentage-based coverage, and ownership over silos. You’ll work on your personal foundation as well as your role within your team and organization.

The training is developed and delivered by Betabit specialists who work on business-critical software every day. Expect interactive propositions, real-world cases, and direct reflection on your own approach.

What you’ll learn

After a joint kickoff where goals and experiences are shared, you’ll work through ten blocks spread over two days. Depending on experience and learning needs, the blocks can be tailored together.

Day 1 – You and your foundation

• The test pyramid in context
  • What the pyramid says and what it doesn’t say
  • Context and modern architectures: when do you consciously deviate
  • Case: draw and compare your own pyramid
• Risk-based testing
  • Identify risks per category and score them on impact × likelihood
  • From priority matrix to focused test charters
  • Reporting on risk status, not just pass or fail
• Agile testing and test quadrants
  • Test quadrants: which type of test, what goal, who is responsible
  • Shift left: embedding quality in refinement and acceptance criteria
  • Go slow to go fast: why early investment speeds things up later
• Test maintenance and sustainability
  • How and why test suites become fragile
  • Structural principles for maintainable test code
  • Test maintenance as part of the Definition of Done
• Personal craftsmanship
  • From executing to influencing: mindset and ownership
  • Making and defending decisions as a professional
  • Personal reflection and growth path

Day 2 – You, your team and the organization

• Effective communication
  • Talk code with developers, talk impact with the business
  • Making risks visible at the right moment
  • Taking a well-founded position when there is resistance on priorities
• Planning and test strategy
  • From test vision to Definition of Done to pipeline
  • Reporting test coverage based on risks and business rules, not percentages
  • Environment stages and gated promotions: quality checks per phase
• Integration and chain quality
  • Contract testing and flow tests as an alternative to end to end bloat
  • Detecting integration issues early: consumer driven contracts and ephemeral environments
  • Testing robustness: timeouts, retries, idempotency and circuit breakers
• Monitoring and shift right
  • Telemetry and observability as part of your test strategy
  • Shift right: synthetic tests, canary metrics and feature usage evaluation
  • Measuring team performance: MTTR, change failure rate and defect escape rate
• Culture of Quality
  • Collective ownership, feedback loops and continuous learning
  • Quality gates, retrospectives, pairing and blameless post mortems
  • Embedding knowledge sharing and the tester as a catalyst for a quality culture

Modernization as a continuous process

After this training, you’ll know how to approach modernization in a structured and responsible way. You’ll recognize outdated patterns, choose the right solutions, and work with your team on software that’s future-ready – better for the user, and more enjoyable to work on.