Thor Release Readiness Checklist - Sunflower

Action	Responsible	Status

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 Trillium backlog	Charlotte, Product owner	Done
All user stories tied to features should be written and estimated.	Charlotte, Product owner	Done
Testing Identify features that require e2e tests Identify features that require Karate tests	Charlotte, product owner together with Thor team	TBD
Conduct user acceptance testing	Charlotte, as Product owner work together with with Thor team
Conduct or create user stories for performance/load testing. See	N/A	-
Document Potential Risks and Risk Mitigation Plan	N/A	-

Action	Responsible	Status

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 Trillium backlog	Charlotte, Product Owner	Done
Prepare data for Bugfest Create user stories for Kitfox that outline your needs and instructions Please consider how to test long lists/tables	Charlotte, Product Owner and Nassib/Corrie	Done
Migration/module upgrade documentation checklist Migration Plan Step by Step instructions for module upgrade New Infrastructure: N/A Config Changes: Schema Changes: JIRA issues created Data Migration: Migration Testing What are the configuration Changes? What are the schema Changes? How do we test?	Index Data
Any breaking changes?	Thor	No
Re-Indexing for release upgrade? For bugfest Sunflower?	-	No
Add release notes Include any previous release notes that still relate to the release flag any known items with the label known-issue-<<release>> See document - Release Notes Overview	Charlotte, as product owner	Has begun adding notes.
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	-	-
Conduct or create user stories for performance/load testing. See Types of tests	N/A	-
Document Potential Risks and Risk Mitigation Plan Risks:	N/A	-

Action	Responsible	Status

Action	Responsible	Status
Update Features' statuses Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders	Charlotte as Product Owner	Done
Prepare data for Bugfest 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	Charlotte working with with KitFox team on bound+with data (BF-773)
Add release notes Include any previous release notes that still relate to the release flag any known items with the label known-issue-<<release>>	Charlotte, as Product Owner together with Team	In progress
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	-	-
Conduct or create user stories for performance/load testing. See Types of tests	N/A	-

Action	Responsible	Status

Action	Responsible	Status
Update Features' statuses Identify which features are at risk and the "at-risk" label to the feature.	Charlotte, Product Owner
User stories: update Release field for those stories/bugs/tasks/etc that will not be done for the release.	Charlotte, Product Owner
Generate Release Artifacts (see Orchid) and link to Release notes	Thor 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>>	Charlotte, Product owner
Modules Ready for deployment Deployment information is provided in launchDescriptor section of module descriptor. Review test status - Unit, Integration, e2e tests https://jenkins-aws.indexdata.com/job/Testing/job/Scheduled%20Karate%20Tests/600/cucumber-html-reports/overview-features.html Tickets will be created automatically for each failure.	Thor team
Team meets with Kitfox to review upgrade instructions. Team's accept Bugfest build. Teams 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?	N/A	-
Regression testing?
Conduct performance/load testing. See Types of tests	Charlotte, Product Owner writes user stories. TBD who will conduct.

Action	Responsible	Status

Action	Responsible	Status
Update Features' statuses There should be no at-risk feature	Charlotte, 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>>	Charlotte, Product owner, and devs at the Thor team.
Complete remaining performance/load testing. See Types of tests	Charlotte, Product Owner writes user stories. TBD who will conduct.

Action	Responsible	Status

Action	Responsible	Status
Teams must conduct smoke tests to verify key functionality works as expected	Thor Team
Testing: All Karate tests and e2e tied to release functionality should be done and running	Thor 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>>	Charlotte as Product owner