Project Completion Steps for Team Bama

Completing feature for a Flower Release requires the completion of the following steps:

1. Functionality completed as per Feature description and presented to PO or Product Council if needed in the team Rancher environment
2. All stories completed as per our Definition of Done (see link) and code is merged into master BEFORE the Feature Freeze milestone (as per Flower Release schedule). 
   1. Code completed with no code smells
   2. unit test coverage in BE and FE at least 80%
   3. Karate tests created and successfully executed, making sure that the existing tests in the given functional area continue to run successfully. Karate test runs are attached to PRs
   4. PRs are approved by at least 2 reviewers (at least one reviewer should be from the team that owns the FOLIO Module in which the feature is implemented)
   5. Approved PR are merged into master
3. Feature tested
   1. test cases are defined and created in TestRail and assigned to Bama
   2. test cases executed manually and all pass. Fix bugs if found.
   3. optional but highly desirable: automate e2e test cases suitable for automation. If automated is done ensure that the automated cases are part of the nightly e2e run
4. Support and maintain your feature during bugfest and beyond
   1. Create release notes for your feature
   2. Review and address bugs found in Bugfest or other environments including production

Addendum

Onboarding a new FOLIO community team (from Wolfcon)