[UXPROD-3454] Cypress test execution on Rancher Created: 15/Dec/21  Updated: 14/Sep/22

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: TBD
Reporter: Dilshod_Khusanov Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by RANCHER-83 Replace steps related with Karate to ... Closed
is defined by RANCHER-84 Setup required components(back,front,... Closed
is defined by RANCHER-87 Tear down of allocated machines after... Closed
is defined by RANCHER-89 Testrail integration Closed
is defined by RANCHER-144 Initial test data management Closed
is defined by RANCHER-184 Manage new portion of deviations in t... Closed
is defined by RANCHER-196 Folio settings update in pipeline2 ba... Closed
is defined by RANCHER-208 Add change of knowledge base credenti... Closed
is defined by RANCHER-80 Folio - Implement Jenkins pipeline to... Closed
is defined by RANCHER-81 Create pipeline for cypress tests Closed
is defined by RANCHER-82 Deploy env. in Rancher Closed
is defined by RANCHER-90 Configure tests artifacts keeping Closed
is defined by RANCHER-86 Parallel run of tests by several agents Closed
is defined by RANCHER-88 Merge test results from each agent in... Closed
is defined by RANCHER-91 Trigger test execution by special con... Closed
is defined by RANCHER-92 Slack notification about failed tests Draft
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R5

 Description   

Purpose/Overview:

 Need to develop special pipeline with main aim - execute existing GUI e2e tests in FOLIO project

Requirements/Scope:

  1. Copy of Karate pipeline
  2. Setup required variables
    "baseUrl": "https://folio-snapshot.dev.folio.org""viewportWidth": 1920,  "viewportHeight": 1080,  "video": false"defaultCommandTimeout": 11000,  "pageLoadTimeout": 120000,  "env": {    "OKAPI_HOST": "folio-snapshot.dev.folio.org",    "OKAPI_TENANT": "diku",    "diku_login": "diku_admin",    "diku_password": "admin"  }
    
  1. Replace steps related with Karate to job related with Cypress
  2. Required stages/steps:
    1. Setup required components
      1. Backend
      2. Frontend
      3. Cypress agents
    2. Initial test data should be presented( the same as in https://folio-snapshot.dev.folio.org/ + guide how to extend it, for example, add OCLC Worldcat authentication)
    3. Parallel run of tests by several agents
      • First agent starts tests by "npx cypress run --spec .\cypress\integration\notes\notes.spec.js"
      • Second - "npx cypress run --spec .\cypress\integration\inventory\actions-menu.spec.js"
      • Agents should be located near frontend and backend
    4. Tear down of allocated machines after tests execution
    5. Merge test results from each agent in one place
    6. Send results to Testrail and updated tests results based on provided id(sandbox in Testrail, manually triggered step for the nearest future)
  3. Tests artefacts should be available 2 weeks as minimum
  4. Add ability to trigger test execution by special conditions
    1. variables
    2. frontend/backend branches in github
  5. Slack notification about failed tests

Acceptance criteria:

  • All defined steps are implemented and stable

 

All points will be moved in subtasks in the nearest future.


Generated at Fri Feb 09 00:32:07 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.