Craftsmanship for Testers

Quality is not a phase

Many teams do a lot of testing, but without a clear strategy behind their choices. Risks remain implicit, test suites become fragile, integration issues surface late, and quality remains the QA department's problem rather than the whole team's.

This training teaches you to tackle that systematically. Not with a checklist, but with a coherent vision of what good testing looks like: 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 shared kickoff where goals and experiences are discussed, we work through all the aspects that develop you into a driven testing professional. Modules can be adjusted based on experience and learning needs.

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
  • Identifying risks by category and scoring on impact × probability
  • From priority matrix to focused test charters
  • Reporting on risk status, not just pass or fail
• Agile testing and test quadrants
  • Test quadrants: what type of test, what goal, who is responsible?
  • Shift-left: embedding quality in refinement and acceptance criteria
  • Go slow to go fast: why investing early accelerates delivery 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 to developers; talk impact to business stakeholders
  • Making risks visible at the right moment
  • Standing your ground on priorities when you face pushback
• Planning and test strategy
  • From test vision to DoD to pipeline
  • Reporting test coverage based on risks and business rules, not percentages
  • Environment phases and gated promotions: quality checks per stage
• Integration and chain quality
  • Contract testing and flow tests as an alternative to E2E 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 postmortems
  • Embedding knowledge sharing and the tester as a catalyst for a quality culture

Craftsmanship as a foundation

After this training, you'll have a context-driven test strategy you can explain and defend. You make risks visible, report meaningfully on coverage, and understand how integration strategy and monitoring contribute to predictable software quality. That's craftsmanship, not as a one-off intervention, but as a structural part of how you and your team work.