...
| Page Properties | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Overrides/Supersedes
This decision was migrated from the Tech Leads Decision Log as part of a consolidation process. The original decision record can be found here.
RFC
N/A
Stakeholders
Mikita SiadykhJohn Coburn Alex Mozolev Zak Burke Michal KuklisIvan Kryzhanovskyi Denys BohdanDmitriy LitvinenkoViktor SorokaAditya matukumalliRichard Redweik
Contributors
Approvers
Background/Context
UI Testing Team would like to propose a solution for replacement of Nightmare UI end-to-end integration tests (which has been not maintained by Folio community since the fall of 2020)
...
Every team will support e-2-e tests for modules according to Team vs module responsibility matrix
Goals
- Automation of e-2-e tests that will:
- Accelerate feedback to dev teams by running these tests frequently (daily). Last attempt to execute manual Smoke test plan had failed: https://foliotest.testrail.io/index.php?/runs/view/1785
- Reduce number of test cases that needs to be executed manually during BugFest
- Create e-2-e tests in stages:
- Smoke - 168 tests
- Critical Path - 254 test cases
- Extended - 141 test case (not the final count)
- Create Jenkins pipeline that will execute these daily against reference environment
- Enable dev teams to run these tests on demand. The above pipeline should have arguments to execute e-2-e test suite against any URL (Team Rancher Environment, Bug Fest, Implementer staging system)
- Automation of e-2-e tests that will:
Documentation
- How to create tests with: Cypress + Bigtest interactors
- Test cases has been documented in TestRail: https://foliotest.testrail.io/index.php?/suites/view/21
Assumptions
List all assumptions that were made when making the decision
Constraints
List any constraints that lead us to make a certain decision
Rationale
Document the thought process, list reasons that lead to the final decision
Decision
Short summary of the decision goes here
Implications
- Pros
- N/A
- Cons
- N/A
Other Related Resources
...