Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Duplicate
-
DevOps Sprint 128, DevOps Sprint 129, Kitfox: sprint 132, DevOps Sprint 130, DevOps Sprint 131, Kitfox: sprint 133
-
8
-
Kitfox
Description
Purpose/Overview:
Need to develop special pipeline with main aim - execute existing GUI e2e tests in FOLIO project
Requirements/Scope:
- Copy of Karate pipeline
- 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" }
- Replace steps related with Karate to job related with Cypress
- Required stages/steps:
- Setup required components
- Backend
- Frontend
- Cypress agents
- 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)
- 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
- Tear down of allocated machines after tests execution
- Merge test results from each agent in one place
- Send results to Testrail and updated tests results based on provided id(sandbox in Testrail
, manually triggered step for the nearest future
)
- Setup required components
- Tests artefacts should be available 2 weeks as minimum
- Add ability to trigger test execution by special conditions
- variables
- frontend/backend branches in github
- 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
- defines
-
UXPROD-3454 Cypress test execution on Rancher
-
- Open
-
- duplicates
-
RANCHER-189 Cypress tests on Rancher
-
- In Review
-
- relates to
-
RANCHER-81 Create pipeline for cypress tests
-
- Closed
-
-
RANCHER-82 Deploy env. in Rancher
-
- Closed
-
-
RANCHER-151 Update Jenkins Allure Plugin
-
- Closed
-
-
RANCHER-196 Folio settings update in pipeline2 based on pipeline1
-
- Closed
-
-
FOLIO-3330 Define required tasks to create CI/CD pipeline to run e2e cypress tests
-
- Closed
-
-
FOLIO-3332 Integrate TestRail with Cypress in CI/CD
-
- Closed
-
- mentioned in
-
Page Loading...