Page Comparison

•  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 

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. 

Testing

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

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 

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

• 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

Please add risks below : 

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

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

From Poppy Releases notes - Do we need to carry them to "Q" release 

• Authority API breaking changes documentation
  • enabling with loadReference=true
• Call number browse data migration documentation 
• Update consortia mod-search documentation (Slava) 
• Permissions (Christine/KG) 
• Authority Auto-linking tenant level  configuration (for non-consortia and consortia) 
• Reindexing improvements based on UXPROD-3936
• Add any new permissions (like

  Jira Legacy
  server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UINOTES-141

  )
• Need to add a note about one instance of quickMARC needs to be run. IOW quickMARC module is not HA
• Also review Poppy (R2 2023) Release Notes to determine if other notes should move over to Q release 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

•  Verify that all test cases/test suits for features are created and PO-verified

•  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 ECS and non-ECS builds. 

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

•  Meet with FSE hosting to review release notes/instructions

•  Conduct performance/load testing. See