Completing feature for a Flower Release requires the completion of the following steps:
- Functionality complete completed as per Feature description and presented to PO or Product Council if needed in the team Rancher environment
- 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).
- Code completed with no code smells
- unit test coverage in BE and FE at least 80%
- Karate tests created , and 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
- PRs are approved by at least 2 reviewers (at least one reviewer should be from EPAM or EBSCO)the team that owns the FOLIO Module in which the feature is implemented)
- Approved PR are merged into master
- Feature tested
- test cases are defined and created in TestRail and assigned to Bama
- test cases executed manually and all pass. Fix bugs if found.
- 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
- Support and maintain your feature during bugfest and in productionbeyond
- Create release notes for your feature
- Review and address bugs found in Bugfest or other environments including production
...