Skip to end of banner
Go to start of banner

Teams to implement UI end to end integration tests

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Status
NOT STARTED
Stakeholders

Mikita Siadykh John Coburn Aliaksei Chumakou 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) 

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:

  1. Stripes framework should support interactors that can be used for both unit and end-2-end tests
  2. Test runner should minimize false negative test results

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:
      1. 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
      2. Reduce number of test cases that needs to be executed manually during BugFest
    • Create e-2-e tests in stages:
      1. Smoke  - 168 tests 
      2. Critical Path - 254 test cases
      3. 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

GitHub Repo

https://github.com/folio-org/stripes-testing



Action items

  •  
  • No labels