You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use cypres for doing end to end UI testing for the annotation-ui.
Right now i run npm run e2e to run these tests locally and then push the code to github. Github actions then deploys the code to staging or production environment.
When i run npm run e2e, cypress opens a chrome instance and runs these tests on my machine and i can actually see the different links being clicked but cypress also allows running the browser in a headless mode which lets you run these tests in a CI/CD pipeline.
So I would like the test step npm run e2e to be added to the deploy-prod and deploy-staging workflow here
The expected result is that, what one is finished developing the software, they just push the code to github and we run the test as part of the deploy pipeline itself and deploy to the appropriate environment only if the test passes. It will help us avoid regression bugs for end to end features.
The text was updated successfully, but these errors were encountered:
We use cypres for doing end to end UI testing for the annotation-ui.
Right now i run
npm run e2e
to run these tests locally and then push the code to github. Github actions then deploys the code to staging or production environment.When i run
npm run e2e
, cypress opens a chrome instance and runs these tests on my machine and i can actually see the different links being clicked but cypress also allows running the browser in a headless mode which lets you run these tests in a CI/CD pipeline.So I would like the test step
npm run e2e
to be added to the deploy-prod and deploy-staging workflow hereThe expected result is that, what one is finished developing the software, they just push the code to github and we run the test as part of the deploy pipeline itself and deploy to the appropriate environment only if the test passes. It will help us avoid regression bugs for end to end features.
The text was updated successfully, but these errors were encountered: