Page Comparison

• 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 

On track.

1/ Need to leave authority record from Nolana as is. Khalilah will send instructions to Kitfox.

2. Once the env is ready, Khallah and Valeri will prep the data for testing

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

Developer facing - Team

Consumer facing - Khalilah + Team

E.g.

Nolana (R3 2022) Release Notes

New App, Known Issues, Permissions - PO

Vijay to work with Pavlo on coming with 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

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