Page Comparison

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

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

Testing

• Identify features that require e2e tests 
• Identify features that require Karate tests
• 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 

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

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

• Test rails: Write/Review test cases 
  • Please consider how to test long lists/tables 

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

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

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

• Conduct performance/load testing. See

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

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

• 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

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