Closed vpode closed 8 months ago
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, Thanks for your answer. I deleted the repository file and now the error message is different. A message box indicates "One or more tests have failed". I copy the error from the log:
2023-02-17T19:48:25.487Z [INFO]: # Executing command: npx wait-on --timeout 60 http://localhost:3000 2023-02-17T19:48:25.850Z [WARNING]: Error: Timed out waiting for: http://localhost:3000 at /codebuild/output/src951633968/src/cmsmedios-ux/node_modules/wait-on/lib/wait-on.js:132:31 at doInnerSub (/codebuild/output/src951633968/src/cmsmedios-ux/node_modules/wait-on/node_modules/rxjs/dist/cjs/internal/operators/mergeInternals.js:22:31) at outerNext (/codebuild/output/src951633968/src/cmsmedios-ux/node_modules/wait-on/node_modules/rxjs/dist/cjs/internal/operators/mergeInternals.js:17:70) at OperatorSubscriber._this._next (/codebuild/output/src951633968/src/cmsmedios-ux/node_modules/wait-on/node_modules/rxjs/dist/cjs/internal/operators/OperatorSubscriber.js:33:21) at OperatorSubscriber.Subscriber.next (/codebuild/output/src951633968/src/cmsmedios-ux/node_modules/wait-on/node_modules/rxjs/dist/cjs/internal/Subscriber.js:51:18) at AsyncAction.work (/codebuild/output/src951633968/src/cmsmedios-ux/node_modules/wait-on/node_modules/rxjs/dist/cjs/internal/observable/timer.js:28:28) at AsyncAction._execute (/codebuild/output/src951633968/src/cmsmedios-ux/node_modules/wait-on/node_modules/rxjs/dist/cjs/internal/scheduler/AsyncAction.js:79:18) at AsyncAction.execute (/codebuild/output/src951633968/src/cmsmedios-ux/node_modules/wait-on/node_modules/rxjs/dist/cjs/internal/scheduler/AsyncAction.js:67:26) at AsyncScheduler.flush (/codebuild/output/src951633968/src/cmsmedios-ux/node_modules/wait-on/node_modules/rxjs/dist/cjs/internal/scheduler/AsyncScheduler.js:38:33) at listOnTimeout (internal/timers.js:557:17) 2023-02-17T19:48:25.855Z [ERROR]: !!! Test execution failed, one or more tests are not passing
Hi @vpode 👋 , thanks for reaching out. I observed that the latest build (164) on your Amplify app d2wao2oyvt6nan
has succeeded. If you are running into issues with Cypress tests, I'll recommend reviewing their troubleshooting guide and also any related issues on their GitHub repository.
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.
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
Additional information
No response