-
Notifications
You must be signed in to change notification settings - Fork 224
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 Issues #3366
Comments
This is FIY only and we need to wait on a fix from Cypress. Not reverting as its not actively breaking anything. |
The package start-server-and-test is not maintained by Cypress.io. It belongs to bahmutov who used to work for Cypress, but not any more. This package does not actually use Cypress automatically. I will also monitor the progress and remind him if necessary. I have given him a few PRs lately which he has also merged. The other issues which you have now bundled into this issue are actually owned by Cypress and I am working with them to get them resolved. They are all just cosmetic issues as far as we know. |
|
I suggest not to bundle multiple issues into one GitHub issue in future as the status becomes very difficult to follow. |
Originally posted by MikeMcC399 January 31, 2023
PR Npm full update #3296 from @brianebeling updated start-server-and-test from 1.14.0 to 1.15.2.
Now when Cypress tests are run, there is a message "is responding with HTTP status code NaN" instead of "is responding with HTTP status code 200".
I reported this regression in issue Startup message "is responding with HTTP status code NaN" bahmutov/start-server-and-test#349.
Originally posted by MikeMcC399 January 4, 2023
There are two errors which show up in the logs of https://github.com/corona-warn-app/cwa-website/actions/workflows/cypress-test-prod.yml
These are known Cypress issues and neither of these messages cause a problem to the cwa-website Cypress test, so they can be ignored for practical purposes.
I did however log them as reproducible issues in the hope that the Cypress experts may fix them in a future Cypress version:
That seem to be most of the current, non important, Cypress or related issues from the to be disabled discussions
The text was updated successfully, but these errors were encountered: