Learning path4 levels27 stepsAbout 33 minutes of reading

Software testingfrom first test to test leader.

Four levels, read in order: what testing is and how to start, the techniques working testers use every day, how professional teams plan and run testing, and how leaders build and measure a test function.

Start at step 1

Level 1

Start hereStudents, teens, and anyone curious. No experience needed.

What testing is, what a bug really is, how to design and report tests, and where the careers lead.

  1. 01ArticleWhat Is Software Testing? A Plain-English IntroductionWhy all software has mistakes in it, and the five ideas the profession is built on.Read →
  2. 02ArticleErrors, Defects, and Failures: What a Bug Really IsThe precise vocabulary testers use, and how severity and priority decide what gets fixed.Read →
  3. 03ArticleYour First Test Cases: Designing Tests That Find ProblemsDesign real tests with equivalence partitioning and boundary values.Read →
  4. 04ArticleHow to Report a Bug So It Actually Gets FixedTurn a failed test into a report a developer can act on.Read →
  5. 05ArticleCareers in Software Quality: Roles, Skills, and First StepsThe roles in software quality and practical first steps, including ISTQB Foundation.Read →

Level 2

FoundationsCareer changers, new testers, and developers who want to test well.

Why quality has a cost, the main kinds of testing, and the everyday tools of the trade: test cases, bug reports, test data, and automation.

  1. 06ArticleInvesting in Testing, Part 1: The Cost of Software QualityThe economics behind every testing decision: what poor quality costs and what testing saves.Read →
  2. 07ArticleFunctional Testing: Accuracy, Suitability, and Interoperability as a Coverage FrameworkWhat it means for software to do the right thing, and how to cover it systematically.Read →
  3. 08Template · 6 minThree test case templates, one workbook.Professional test case formats you can copy and use.Read →
  4. 09Checklist · 5 minWrite bug reports developers act on.The full ten-step bug reporting process behind the Start here primer.Read →
  5. 10ArticleA Few Thoughts on Test DataTests are only as good as the data they run on.Read →
  6. 11ArticleInvesting in Testing, Part 5: Manual or Automated?When to test by hand, when to automate, and why the answer is usually both.Read →

Level 3

PractitionerWorking testers, test analysts, and automation engineers.

Risk-based testing from analysis to reporting: decide what matters most, plan around it, run it, measure coverage, and test the hard parts.

  1. 12Checklist · 6 minPrioritize risk before you prioritize tests.Rank what could go wrong by likelihood and impact, so effort goes where failure costs most.Read →
  2. 13ArticleMatching Test Techniques to the Extent of Testing: A Heuristic Framework for Risk-Based Test DesignChoose test techniques in proportion to the risk of each area.Read →
  3. 14Template · 6 minThe test plan structure that actually gets read.Capture scope, approach, and exit criteria in a plan the business can sign.Read →
  4. 15ArticleTest Execution Processes: Managing the Search for the UnexpectedRun testing as a managed process, not a scramble before release.Read →
  5. 16ArticleMeasuring Confidence Along the Dimensions of Test CoverageMeasure how much of the system your tests actually exercise.Read →
  6. 17ArticleProperty-Based and Random-Input Testing: Low-Cost Automation Patterns for Defect Classes Example-Based Testing Cannot ReachLow-cost automation patterns that find defects hand-written tests miss.Read →
  7. 18ArticleSystem Integration Testing: Properties of a Mature SIT PracticeTest the connections between systems, where many serious failures hide.Read →
  8. 19ArticleRisk-Based Test Results Reporting: Four Approaches for Risk-Aware Release DecisionsReport results in terms of risk, so release decisions are informed ones.Read →
  9. 20ArticleEvaluation Before Shipping: How to Test an AI Application Before It Hits ProductionApply the same discipline to AI features, whose answers can change without warning.Read →

Level 4

LeaderTest leads, test managers, and engineering leaders.

Estimate, staff, report, and measure a test function, and improve it with Rex Black's Critical Testing Processes framework.

  1. 21ArticleTest Estimation: Realistic, Actionable, FlexibleEstimates that are realistic, actionable, and flexible enough to survive the project.Read →
  2. 22ArticleHiring and Developing Test Staff: Attributes, Skills, and Continuous Capability GrowthBuild a team with the right mix of skills, and keep growing it.Read →
  3. 23ArticleEffective Test Status Reporting: Facts, Framing, and the Bearer of Bad NewsTell leadership the truth about quality, including when the news is bad.Read →
  4. 24ArticleMetrics for Software Testing, Part 1: The Why and How of MetricsChoose metrics that drive good decisions instead of gaming.Read →
  5. 25ArticleCritical Testing Processes: A Non-Prescriptive Framework for Test Process ImprovementThe framework we use to assess and improve a client's test function.Read →
  6. 26ArticleThe Case for Investing in Testing: A Board-Level Argument for Enterprise Test-Function CapabilityMake the board-level case for investing in testing capability.Read →
  7. 27Cert roadmap · 10 minThe ISTQB Advanced Level path, mappedPlan the next certifications for yourself and your team.Read →

For teams

Taking a whole team through this?We teach it, coach it, and certify it.

Training and certificationTeam coaching

Keep reading

Related reading

Practices

Where this leads

Working on something like this?Talk to the people who wrote it.

Book a call