Test Closure Report — Product Name / Release

Report ID: TCR-XXX Prepared by: Name Date: YYYY-MM-DD Release: v0.0 Test period: Start date → End date Status: Final

---

1. Release Summary

Briefly state what was released, to whom, and on what date. Include a reference to the go/no-go decision.

---

2. Objectives Assessment

Review each test objective from the Test Plan and state whether it was met.

Objective	Met?	Notes
Objective 1	✓ / ✗ / Partial	Comment
Objective 2	✓ / ✗ / Partial	Comment

---

3. Final Test Metrics

Metric	Value
Total test cases planned	X
Total test cases executed	X
Pass rate	X%
Total defects raised	X
Defects resolved before release	X
Defects deferred to backlog	X
Known issues in production	X

---

4. Deferred Defects and Known Issues

List any defects that were accepted and deferred, with the business justification.

ID	Title	Severity	Deferred Reason	Target Fix
BUG-XXX	Title	Sev	Business reason	Version or date

---

5. Exit Criteria Assessment

Exit Criterion	Target	Achieved	Met?
Test execution	≥ X%	X%	✓ / ✗
Critical defects open	0	X	✓ / ✗
High defects open	0	X	✓ / ✗
Regression pass rate	≥ X%	X%	✓ / ✗
UAT sign-off	Required	Status	✓ / ✗

---

6. Lessons Learned

6.1 What Worked Well

• Point 1
• Point 2

6.2 What Could Be Improved

• Point 1
• Point 2

6.3 Recommendations for Next Release

• Recommendation 1
• Recommendation 2

---

7. Deliverables Produced

Deliverable	Location	Status
Test plan	Link	Complete
Test cases	Test management tool	Complete
Test summary report	Link	Complete
Defect log	Jira / Linear link	Complete
Automation results	CI dashboard link	Complete

---

8. Sign-Off

Name	Role	Signature	Date
Name	QA Lead
Name	Product Owner
Name	Dev Lead

Test Closure Report — Novu Bank Mobile App v3.2

Report ID: TCR-2024-032 Prepared by: Priya Mehta Date: 2024-03-15 Release: v3.2.0 Test period: 2024-03-06 → 2024-03-14 Status: Final

---

1. Release Summary

Novu Bank Mobile App v3.2.0 was released to the App Store and Google Play on 2024-03-14 at 16:00 UTC following a successful UAT sign-off by Clara Whitfield (Product Owner) at 13:45 UTC. The go/no-go meeting on 2024-03-14 at 14:00 UTC approved the release after NOVU-2041 and NOVU-2042 were verified resolved in QA earlier that morning.

The release delivers three main features: Open Banking integration with three providers, biometric re-authentication for high-value transfers, and an overhauled notifications centre.

---

2. Objectives Assessment

Objective	Met?	Notes
Open Banking flows complete across all three providers	✓	GreenPay, ClearLedger, OpenRoute all verified in QA and UAT
Biometric re-auth prompts correctly for transfers > £500	✓	Tested on iOS 17.4/17.5 and Android 14
Notifications centre persists preferences across restarts	✓	100% pass rate on preference persistence test cases
No regressions in core payment, statement, or login flows	Partial	4 Appium regression tests quarantined (flaky, not feature regressions) — root cause deferred

---

3. Final Test Metrics

Metric	Value
Total test cases planned	322
Total test cases executed	322
Pass rate	93.2% (300 / 322)
Total defects raised	11
Defects resolved before release	11
Defects deferred to backlog	1
Known issues in production	0 Critical; 0 High

---

4. Deferred Defects and Known Issues

ID	Title	Severity	Deferred Reason	Target Fix
NOVU-2051	Notifications centre: badge count not cleared on Android after mark-all-read	Low	Low user impact; cosmetic; no data risk	v3.2.1 (April)

---

5. Exit Criteria Assessment

Exit Criterion	Target	Achieved	Met?
Test execution	≥ 95%	100%	✓
Critical defects open	0	0	✓
High defects open	0	0 (both fixed 2024-03-14)	✓
Regression pass rate	≥ 98%	97.6% (excl. quarantined)	Conditional ✓
UAT sign-off	Required	Obtained 2024-03-14 13:45	✓

Note: The regression pass rate of 97.6% fell marginally below the 98% target due to four quarantined Appium tests. The steering group accepted this on the grounds that the failures were infrastructure-related (simulator timing), not feature regressions. Decision documented in JIRA NOVU-2055.

---

6. Lessons Learned

6.1 What Worked Well

• Daily 10-minute defect triage (introduced Sprint 23) kept blockers moving — no defect was unassigned for more than 4 hours.
• Exploratory sessions produced two High-severity bugs that scripted testing would not have caught (NOVU-2041, NOVU-2042).
• Close collaboration with the Platform team to stabilise the Open Banking sandbox ahead of Sprint 24 eliminated the instability seen in Sprint 23.
• Written exploratory debrief notes allowed regression case authoring to happen asynchronously, removing a daily hand-off meeting.

6.2 What Could Be Improved

• Build delivery was 5 hours late on Day 1, compressing the execution window. A build-readiness checklist and an earlier daily sync with Dev would help.
• The severity guide didn't adequately cover async-flow failures (e.g., provider redirect timeouts). NOVU-2041 was initially logged as Medium and only escalated after QA review.
• Four Appium regression tests were not identified as flaky until they had failed on multiple runs. Automated flake detection in CI should be added.

6.3 Recommendations for Next Release

• Add a build-readiness checklist item to the Sprint kick-off template.
• Update the defect severity guide with async and external-provider failure examples before the v3.3 test plan is written.
• Implement automated flaky-test detection in CI (quarantine after ≥ 2 failures in 5 runs).
• Schedule the Open Banking mid-redirect bank session expiry scenario as a dedicated test in v3.3 once product has clarified expected behaviour.

---

7. Deliverables Produced

Deliverable	Location	Status
Test plan	Confluence/NOVU-TP-3.2	Complete
Test cases	Jira NOVU-1892 (322 cases)	Complete
Test summary report	TSR-2024-032	Complete
Defect log	Jira NOVU-QA-DEFECTS-3.2	Complete
Automation results	CI Dashboard / Sprint 24	Complete
Exploratory debrief notes	Confluence/NOVU-EXP-3.2	Complete

---

8. Sign-Off

Name	Role	Signature	Date
Clara Whitfield	Product Owner	✓	2024-03-14
Priya Mehta	QA Lead	✓	2024-03-15
Ayo Adeyemi	Dev Lead	✓	2024-03-14