Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
\uD83D\uDCAD Checklist
Testing
- Identify tickets that require UI load testing for long lists/tables.
- Identify tickets that require Karate tests.
- Identify tickets that require performance testing.
Delivery
- Review completed tickets and decide if release notes should be updated:
- Required migrations
- Config changes
- New/changed permissions
- Breaking schema changes
- Re-indexing changes
- Known issues
- MARC mappings changes
- What else?
- Document potential risks and risk mitigation plan
- Call number issues - the risks are: 1) will not be able to fix them all 2) it might affect the existing implementation → mitigation is a refactoring feature planned for S release