-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cypress testing is not executed in the deploy #3235
Comments
Hi @vpode, apologies for the delay here. There is an amplify.yml file in the root of your repository and it doesn't include a test phase. The amplify.yml file is going to take precedence over the build commands that are defined in the console. This is why you have successful builds without the test phase completing. To resolve this, you should either remove the amplify.yml file in your repository or update the file with the desired test phase. |
Hi @hloriana, 2023-02-17T19:48:25.487Z [INFO]: # Executing command: npx wait-on --timeout 60 http://localhost:3000 |
Hi @vpode 👋 , thanks for reaching out. I observed that the latest build (164) on your Amplify app |
This issue is now closed. Comments on closed issues are hard for our team to see. |
This issue has been automatically locked. |
Before opening, please confirm:
App Id
/d2wao2oyvt6nan
AWS Region
us-east-1
Amplify Hosting feature
E2E Cypress tests, Frontend builds
Describe the bug
We have an angular front-end hosted in aws amplify.
Recently we tried to add cypress e2e testing.
(using "ng add @cypress/schematic " in the proyect)
We create 3 tests inside the folder : "/cypress/e2e"
We followed this guide:
https://docs.aws.amazon.com/amplify/latest/userguide/running-tests.html
And deployed the app in amplify (using a git commit).
But, this doesnt work:
The compilation ends, but with no testing "stage". We read under it: "Test is still pending or has been cancelled for this build."
Expected behavior
We expect to see a execution of the e2e test and a "verify" tab with the results.
Reproduction steps
Build Settings
Log output
The text was updated successfully, but these errors were encountered: