Uploaded image for project: 'rancher'
  1. rancher
  2. RANCHER-189

Cypress tests on Rancher

    XMLWordPrintable

Details

    • Epic
    • Status: Open (View Workflow)
    • TBD
    • Resolution: Unresolved
    • Cypress tests on Rancher
    • None
    • TBD

    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.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              Vitaly_Demchenko@epam.com Vitaly Demchenko
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: