Release Readiness Checklist - Orchid

• Update Features' statuses

• Identify which features are at risk and the "at-risk" label to the feature.  

Product owner

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

Product owner

Testing 

• Identify remaining Karate tests to complete for the module release 

• Identify automated e2e test cases to complete by start of bugfest

• Identify the cases in our functionality consumed by other modules and create test for functionality collaboration 

Team

Conduct user acceptance testing 

• Product owner (maybe a SIG member can help write tasks?) 

• Team needs to setup an environment for UAT

Likely to begin during the week of 02.13

Conduct or create user stories for performance/load testing. See Types of tests

Team

Haven't  done this yet

• Update Features' statuses

• Identify which features are at risk and the "at-risk" label to the feature.  

Product Owner

• Test rails: Write/Review test cases 

  • Please consider how to test long lists/tables 

Product Owner/Manual QA/SIG

Mainly to account for boundary conditions. Ideal to have this as part of the user story

• 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 

Team

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

Team

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 

Team

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

Types of tests

Team

• Update Features' statuses

• Identify which features are at risk and the "at-risk" label to the feature.

Product Owner

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

Product Owner

• 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

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

Team

• Conduct performance/load testing. See

Types of tests

Team

• Update Features' statuses

• There should be no at-risk features

Team

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

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

Team

• Complete remaining performance/load testing. See

Types of tests

Team/PTF

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

Team

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

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

Team