Testing, Bugs, and QA for Product Managers

A failing test, a known checkout defect and an approaching launch create different questions about risk. Testing, Bugs, and QA for Product Managers explains the checks behind those questions and how to discuss their results with Engineering and QA. It examines what has been validated, what remains uncertain and who could be affected.

Understand what the tests cover

The book introduces software quality and the reasons defects appear, then explains how different tests contribute to the evidence available before a release. Its coverage includes:

• Unit, integration and end-to-end tests, alongside functional, regression, smoke and non-functional testing.
• The testing pyramid, automation, manual checks, test cases, environments and test data.
• Acceptance criteria, test coverage, passing and failing results and flaky tests.
• Severity, priority and the impact of bugs on users and the business.
• Release decisions with known defects and the assessment of remaining risks.
• Quality improvements, testing debt and metrics for planning the work.

Connect the results to product decisions

The examples follow Mercato, a fictional commerce platform, through checkout, payments, promotions and returns. These situations place test results and defects within the customer journey, giving context to bug triage, backlog decisions and discussions about what to fix before release.

The material is intended for Product Managers, Product Owners and product professionals working with development teams. It starts with the fundamentals and does not require programming experience. Each test result is examined alongside its scope and limitations to inform a specific quality decision.

For related delivery and investigation work, see CI/CD and Releases for Product Managers and Logs, Kibana, and Observability for Product Managers. Technical Debt for Product Managers covers the prioritization of longer-term technical improvements.