Release Readiness Checklist - Poppy

• Update Features' statuses
• Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders
• Clean up Poppy backlog 

• All user stories tied to features should be written and estimated. 

Testing

• Identify features that require e2e tests 
• Identify features that require Karate tests

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? 

We probably need a "Q" feature? Will determine based on dependencies?   

What about consortia specific e2e tests > TBD but not considered for Poppy.

• Conduct user acceptance testing 

• Product owner (maybe a SIG member can help write tasks?) 
• Team needs to setup an environment for UAT

• Conduct or create user stories for performance/load testing. See

• Document Potential Risks and Risk Mitigation Plan

• Update Features' statuses
• Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders
• Clean up Poppy backlog

• Prepare data for Bugfest
• Create user stories for Kitfox that outline your needs and instructions
• Please consider how to test long lists/tables 

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?

Any breaking changes? 

Re-Indexing for release upgrade? For bugfest? Consortia test environment? 

• Required
• Timing 

• Production libraries = Yes 
  • Dependency is on PTF stories. Follow up with Martin and DA. 
• Bugfest = Yes
  • Dependency is on PTF stories. Follow up with Martin and DA. 
• Consortia integration environment = N/A it is new 

Need to add release notes

• 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

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

Document Potential Risks and Risk Mitigation Plan

Risks:

• Linking (consortia) feature 
• Folijet development... dependencies 
• Call number browse by type feature (migration) 
  • We need to talk with FSE hosting 

Did the 9/14 discussion happen? 

Christine has created a decision log 

Meeting with POs + QA for 9/27 

• Update Features' statuses
• Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders

• 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 

• Add release notes 
  • Include any previous release notes that still relate to the release 
  • flag any known items with the label  known-issue-<<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 

• Conduct or create user stories for performance/load testing. See

• Update Features' statuses
• Identify which features are at risk and the "at-risk" label to the feature.

• User stories: update Release field for those stories/bugs/tasks/etc that will not be done for the release. 

• Generate Release Artifacts (see Orchid) and link to Release notes 

• Add release notes 
  • Include any previous release notes that still relate to the release 
  • flag any known items with the label  known-issue-<<release>>

• 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. 

Team meets with Kitfox to review upgrade instructions. 

Team's accept Bugfest build. Need to consider Consortia support. 

• 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? 

• Conduct performance/load testing. See

• Update Features' statuses
• There should be no at-risk feature 

• 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>>

• Complete remaining performance/load testing. See

• Teams must conduct smoke tests to verify key functionality works as expected

Testing: All Karate tests and e2e tied to release functionality should be done and running 

• 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>>