Test plan
Scope, approach, schedule, risks, entry/exit criteria. IEEE 829-style structure.
640 wordsIEEE 829ReleasePlanning
Test Plan ā Product Name v0.0
Document ID: TP-XXX Author: Name Date: YYYY-MM-DD Status: Draft / Review / Approved
1. Introduction
1.1 Purpose
State what release, feature set, or test cycle this plan covers and why it exists.
1.2 Scope
In scope:
- Feature or component 1
- Feature or component 2
Out of scope:
- Excluded area ā reason
1.3 References
- PRD / user story link
- Previous test plan (if applicable)
2. Test Objectives
List what testing will confirm or measure. Use numbered points.
- Objective 1
- Objective 2
3. Testing Approach
3.1 Test Types
| Type | Scope | Owner |
|---|---|---|
| Smoke | Scope | Role |
| Regression | Scope | Role |
| Exploratory | Scope | Role |
| Performance | Scope | Role |
| UAT | Scope | Role |
3.2 Test Techniques
Describe the design techniques to be used: equivalence partitioning, boundary value analysis, exploratory charters, etc.
4. Entry and Exit Criteria
4.1 Entry Criteria
- Build deployed to test environment
- Smoke suite passes with 0 blockers
- Test data prepared and verified
4.2 Exit Criteria
- ā„ X% of planned test cases executed
- 0 open Critical or High severity defects
- Regression pass rate ā„ X%
- UAT sign-off obtained
5. Environments and Test Data
| Environment | URL / Details | Owner |
|---|---|---|
| Test | URL | Name |
| Staging | URL | Name |
Describe test data sources and how data will be set up / torn down.
6. Schedule and Milestones
| Milestone | Target Date | Owner |
|---|---|---|
| Test planning complete | Date | Name |
| Test case review | Date | Name |
| Test execution start | Date | Name |
| Automation run complete | Date | Name |
| UAT | Date | Name |
| Test summary report | Date | Name |
| Go / no-go decision | Date | Name |
7. Risks and Mitigations
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Risk description | High / Medium / Low | High / Medium / Low | Mitigation plan |
8. Roles and Responsibilities
| Role | Name | Responsibility |
|---|---|---|
| QA Lead | Name | Planning, reporting, stakeholder communication |
| QA Engineer | Name | Test design and execution |
| SDET | Name | Automation and performance tests |
| Product Owner | Name | UAT sign-off |
| Dev Lead | Name | Defect triage and fix delivery |
9. Deliverables
- Test cases in test management tool
- Daily status updates in channel
- Test summary report
- Defect log export
10. Approvals
| Name | Role | Signature | Date |
|---|---|---|---|
| Name | Role | ||
| Name | Role |
Test Plan ā Novu Bank Mobile App v3.2
Document ID: TP-2024-032 Author: Priya Mehta Date: 2024-03-01 Status: Approved
1. Introduction
1.1 Purpose
This plan covers regression and feature testing for Novu Bank Mobile App v3.2, which introduces Open Banking integration, biometric re-authentication for high-value transfers, and an overhauled notifications centre.
1.2 Scope
In scope:
- Open Banking: link/unlink external accounts, balance view, transaction import
- Biometric re-auth: FaceID and Fingerprint flows on iOS 17+ and Android 14+
- Notifications centre: preference management, push delivery, in-app bell icon
- Full regression of core payment and transfer flows
Out of scope:
- Web dashboard (separate release cadence)
- Third-party Open Banking provider certification (handled by provider)
- Accessibility audit (scheduled for v3.3)
1.3 References
- PRD: Confluence/NOVUBANK-PRD-3.2
- Previous plan: TP-2024-028 (v3.1)
- Jira epic: NOVU-1892
2. Test Objectives
- Confirm Open Banking flows complete successfully across all three supported providers in the sandbox environment.
- Verify biometric re-auth prompts correctly for transfers above Ā£500 and enrols new devices without data loss.
- Confirm the notifications centre persists preferences across app restarts and OS-level notification toggles.
- Confirm no regressions in core payment, statement, or login flows.
3. Testing Approach
3.1 Test Types
| Type | Scope | Owner |
|---|---|---|
| Smoke | Core login, balance, transfer | QA Lead |
| Feature | Open Banking, biometric re-auth, notifications centre | QA Team |
| Regression | 210-case regression suite (Appium) | SDET |
| Exploratory | Open Banking consent flow edge cases | QA Team |
| Performance | Transfer API under 200 concurrent users | SDET |
| UAT | Open Banking happy path sign-off | Product Owner |
3.2 Test Techniques
- Equivalence partitioning for transfer amounts (below / at / above Ā£500 threshold)
- Boundary value analysis for notification preference flag combinations
- Session-based exploratory testing: 2 Ć 90-minute sessions on the Open Banking consent flow
4. Entry and Exit Criteria
4.1 Entry Criteria
- v3.2 build deployed to QA environment with release notes
- Smoke test suite passes (0 blockers)
- Test data: 4 linked external accounts in Open Banking sandbox, seeded biometric enrolment data
- All three Open Banking sandbox providers confirmed available
4.2 Exit Criteria
- ā„ 95% of planned test cases executed
- 0 open Critical or High severity defects
- Appium regression pass rate ā„ 98%
- UAT sign-off obtained from Product Owner
5. Environments and Test Data
| Environment | URL / Details | Owner |
|---|---|---|
| QA | qa.novubank.internal | QA Ops |
| Performance | perf.novubank.internal | SDET |
| iOS devices | iPhone 13 (iOS 17.4), iPhone 15 (iOS 17.5) | QA device pool |
| Android devices | Pixel 7 (Android 14), Samsung S24 (Android 14) | QA device pool |
Test data managed in Confluence/NOVU-TEST-DATA-3.2. Sandbox Open Banking accounts provisioned via NovuTestHarness CLI.
6. Schedule and Milestones
| Milestone | Target Date | Owner |
|---|---|---|
| Test planning complete | 2024-03-01 | Priya Mehta |
| Test case review | 2024-03-04 | Full QA team |
| Test execution start | 2024-03-06 | QA team |
| Automation run complete | 2024-03-10 | Dev Patel |
| Exploratory sessions | 2024-03-11 | QA team |
| UAT | 2024-03-12 | Clara Whitfield |
| Test summary report | 2024-03-13 | Priya Mehta |
| Go / no-go decision | 2024-03-14 | Steering group |
7. Risks and Mitigations
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Open Banking sandbox instability | Medium | High | Parallel testing on live sandbox; fallback to mocked responses |
| Biometric hardware availability | Low | Medium | 2 iOS + 2 Android reserved; simulators as backup |
| Late build delivery | Medium | High | Prioritise critical path; defer exploratory if schedule slips |
| UAT participant unavailability | Low | Medium | Reserve backup participant from customer panel |
8. Roles and Responsibilities
| Role | Name | Responsibility |
|---|---|---|
| QA Lead | Priya Mehta | Planning, reporting, stakeholder communication |
| QA Engineer | Marcus Obi | Feature test cases, manual execution |
| QA Engineer | Sasha Koval | Regression execution, defect logging |
| SDET | Dev Patel | Appium automation, performance tests |
| Product Owner | Clara Whitfield | UAT sign-off |
| Dev Lead | Ayo Adeyemi | Defect triage, fix delivery |
9. Deliverables
- Test cases in Jira (linked to NOVU-1892)
- Daily status updates in Slack #qa-v3-2
- Test summary report (TP-SUMMARY-3.2)
- Defect log export
10. Approvals
| Name | Role | Signature | Date |
|---|---|---|---|
| Clara Whitfield | Product Owner | ā | 2024-03-02 |
| Priya Mehta | QA Lead | ā | 2024-03-01 |
| Ayo Adeyemi | Dev Lead | ā | 2024-03-02 |
// Related templates
Test strategy
High-level testing approach for an entire product or release programme. Org-level document.
Risk assessment
Product/release risk register with likelihood, impact, and mitigation per risk.
Release readiness checklist
Pre-release sign-off checklist covering testing, monitoring, rollback, and comms.