Spitfire Release Readiness Checklist - Q
Each sprint
Action | Responsible | Status |
|---|---|---|
Review tickets and decide if Release notes should be updated
needs-releasenote-quesnelia
needs-releasenote-poppy
| Team | Sprint 187 Note: Q release Jira ticket |
Verify that all test cases/test suits for features are created and PO-verified | QA + POs | Sprint 187 Sprint 188 Sprint 189 |
Two sprints before feature freeze (184)
Action | Responsible | Status |
|---|---|---|
Update Features' statuses Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders Clean up Q backlog | Product owner | feature list is accurate and up-to-date
Natalia: to move tickets with release field "R" to the next release |
All user stories tied to features should be written and estimated. | Product owner | Natalia: to double -ckeck user stories |
Testing Identify features that require e2e tests Identify features that require Karate tests | Team | From Poppy Release notes discussion Need Karate tests for consortia > Action item to create consortia specific Karate tests stories. So no expectation that these stories will be ready for Dev freeze and for Go-Live? What about consortia specific e2e tests |
Conduct user acceptance testing |
| Goal Sprint 186 - need rancher environment to be updated. |
Conduct or create user stories for performance/load testing. See | Product Owner writes user stories. TBD who will conduct. | no need in PTF testing, Valery will create his own tests |
Document Potential Risks and Risk Mitigation Plan | Team |
|
One sprint before feature freeze (185)
Action | Responsible | Status |
|---|---|---|
Update Features' statuses Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders Clean up Q backlog | Product Owner |
|
Prepare data for Bugfest Create user stories for Kitfox that outline your needs and instructions Please consider how to test long lists/tables | Team |
|
Migration/module upgrade documentation checklist Migration PlanStep by Step instructions for module upgrade New Infrastructure: N/A Config Changes: Schema Changes: JIRA issues created Data Migration: Migration TestingWhat are the configuration Changes? What are the schema Changes? How do we test? | Team |
|
Any breaking changes? | Team |
|
Re-Indexing for release upgrade? For bugfest? Consortia test environment?Required Timing |
|
|
| PO and Dev lead | From Poppy Releases notes - Do we need to carry them to "Q" release
|
Accessibility Testing Run automated accessibility testing IF you have RTL/JEST tests review (https://github.com/nickcolley/jest-axe)' OR conduct manual accessibility testing with Deque aXe | Team |
|
Conduct or create user stories for performance/load testing. See Types of tests | Team |
|
Document Potential Risks and Risk Mitigation PlanPlease add risks below : | Team |
|
Feature freeze sprint (186)
Action | Responsible | Status |
|---|---|---|
Update Features' statuses Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders | Product Owner |
|
Prepare data for Bugfest (ECS and non-ECS) Create user stories for Kitfox that outline your needs and instructions FWIW - I think settings needs to be cleaned Please consider how to test long lists/tables | Team |
|
| PO and Dev lead | From Poppy Releases notes - Do we need to carry them to "Q" release
|
Accessibility Testing Run automated accessibility testing IF you have RTL/JEST tests review (https://github.com/nickcolley/jest-axe)' OR conduct manual accessibility testing with Deque aXe | Team |
|
Conduct or create user stories for performance/load testing. See | Product Owner writes user stories. TBD who will conduct. |
|
Verify that all test cases/test suits for features are created and PO-verified | QA + POs |
|
Sprint before Bugfest (aka Business Acceptance Testing) period (187)
Action | Responsible | Status |
|---|---|---|
Update Features' statuses Identify which features are at risk and the "at-risk" label to the feature. | Product Owner |
|
User stories: update Release field for those stories/bugs/tasks/etc that will not be done for the release. | Product Owner |
|
Generate Release Artifacts (see Orchid) and link to Release notes | Team |
|
Add release notes Include any previous release notes that still relate to the release flag any known items with the label known-issue-<<release>> | PO and Dev lead |
|
Modules Ready for deployment Deployment information is provided in launchDescriptor section of module descriptor. Review test status - Unit, Integration, e2e tests Tickets will be created automatically for each failure. | Team |
|
Team meets with Kitfox to review upgrade instructions. Team's accept Bugfest ECS and non-ECS builds. QA Team must conduct smoke tests to verify key functionality works as expected BEFORE Bugfest is made available to community Teams must document App/module not ready for testing Issues yet to be resolved Deployment verification(check if functionality works as expected) | Team |
|
Meet with FSE hosting to review release notes/instructions | Team |
|
Conduct performance/load testing. See | Product Owner writes user stories. TBD who will conduct. |
|
Sprint before GO-Live
Action | Responsible | Status |
|---|---|---|
Update Features' statuses There should be no at-risk feature | Product Owner |
|
Add/Review release notes Include any previous release notes that still relate to the release flag any known items with the label known-issue-<<release>> | PO and Dev lead |
|
Complete remaining performance/load testing. See | Product Owner writes user stories. TBD who will conduct. |
|
Go-Live sprint
Action | Responsible | Status |
|---|---|---|
Teams must conduct smoke tests to verify key functionality works as expected | Team |
|
Testing: All Karate tests and e2e tied to release functionality should be done and running | Team |
|
Add/Review release notes Include any previous release notes that still relate to the release flag any known items with the label known-issue-<<release>> | PO and Dev lead |
|