The card below is the “product under test”. Use guided mode to see the bug list upfront, or blind mode to find them yourself first.
Techniques: Test planning, Test estimation
Test Strategy — Customer Portal v2.1
Author: James T. • Sprint 14 • Reviewed: No
Scope
We will test the login, dashboard, and report download features. Out of scope: billing, admin panel, API.
Test types
- Functional testing (happy path only)
- Regression testing of changed components
Environments
Testing will be done in the developer’s local environment.
Test data
We will use real production data for testing.
Entry criteria
Testing begins when the developer says it’s ready.
Exit criteria
Testing is complete when all test cases pass.
Risks
None identified.
Your findings
0 / 0 bugs foundTick each bug as you confirm it on the page above. Progress saves automatically.
Write down every bug you find. Be specific — where it is, what’s wrong, what it should be.
Planted bugs (6)
- A strategy that only tests the happy path will miss all negative, boundary, and error cases — this is a critical gap.
- Testing in a local environment means results won't reflect staging or production configuration, dependencies, or data. Should use a shared test environment.
- Using production data for testing is a privacy/compliance risk (PII exposure) and a data integrity risk (tests may modify or delete real records).
- Entry criteria should be objective and measurable — e.g. 'build deployed to test env, smoke tests passing, no P1 open defects'. Subjective criteria can't be audited.
- 'All test cases pass' is not sufficient exit criteria — it depends on the quality of the test cases. Should include: no open High/Critical defects, regression suite green, sign-off from stakeholders.
- No software project has zero risk. This signals the risk assessment was skipped, not that risks don't exist. A test lead should always name at least: timeline risk, environment risk, data risk.
Strategy review: read each section and ask — is this specific enough to be actionable? Is it safe? Is it complete? Could a different tester follow this without asking questions?