Teams to implement UI end to end integration tests
Status | NOT STARTED |
|---|---|
Stakeholders | Mikita Siadykh John Coburn Alex Mozolev Zak Burke Michal Kuklis Ivan Kryzhanovskyi Denys Bohdan Dmitriy Litvinenko Viktor Soroka Aditya matukumalli Richard Redweik Igor Godlevskyi (Deactivated) |
Outcome | |
Due date | |
Owner | Anton Emelianov (Deactivated) |
NOTICE
This decision has been migrated to the Technical Council's Decision Log as part of a consolidation effort. See: DR - DR-000031 - Teams to implement UI end to end integration tests
Background
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)
Requirements:
Stripes framework should support interactors that can be used for both unit and end-2-end tests
Test runner should minimize false negative test results
Every team will support e-2-e tests for modules according to FOLIO Module/JIRA project-Team-PO-Dev Lead 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)
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
GitHub Repo
Action items