Automation QA enablers (FAT-1092)

[FOLIO-3330] Define required tasks to create CI/CD pipeline to run e2e cypress tests Created: 03/Nov/21  Updated: 30/Nov/21  Resolved: 30/Nov/21

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None
Parent: Automation QA enablers

Type: Task Priority: TBD
Reporter: Oleksii Petrenko Assignee: Dmitry
Resolution: Done Votes: 0
Labels: AQA, epam-spitfire
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to RANCHER-80 Folio - Implement Jenkins pipeline to... Closed
relates to UXPROD-3398 Spitfire: e2e tests - PoC | R1 2022 L... Closed
relates to FAT-1111 Setup Cypress Dashboard service Closed
Sprint: eHoldings Sprint 128
Story Points: 2
Development Team: Spitfire
Epic Link: Automation QA enablers

 Description   
  1. review actual yml file
  2. discuss suggestions with DevOps team

Main vision - make copy of Karate pipeline with regular run(daily)

Suggested tasks to DevOps related with pipeline v0.1:

  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/)
    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


 Comments   
Comment by Dmitry [ 16/Nov/21 ]

current snapshot issues:

  • location is not fixed. Naming + validation rules can be changed now in any moment 
Comment by Dmitry [ 26/Nov/21 ]

implementation moved to DevOps in RANCHER-80

Generated at Thu Feb 08 23:27:18 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.