-
Notifications
You must be signed in to change notification settings - Fork 24
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
Establish reliable CI pipeline #287
Comments
#268 makes CI pipeline incredibly unreliable. |
Consider rendering scenario anew for each test, instead of relying on interactive methods like |
|
One of the reasons the current integration tests are not reliable may be related to the side-effects in I have removed integration tests from the build pipeline for now. Tests still run on local to ensure nothing is broken. I think Form-Field communication needs to be refined to remove mentioned side-effects, and be more bulletproof. It may be a good opportunity for #232. |
The reliability of the CI is highly dependent on the #324. |
Environment
What
I suggest to consider the necessity of explicit
cy.wait
in the integration tests.Why
Using timeouts may be suitable in some cases, but I am growing worried that the library responsiveness may be in risk. The reason of using timeouts is (probably) related to the form not being fully bootstrapped before trying to run assertions on it, or its fields.
How
This is also a task to establish a reliable CI pipeline. I hate to see current setup producing falsy negative results during integration tests, this is unacceptable. Need to figure out why this happens, and how to eradicate it at its core.
The text was updated successfully, but these errors were encountered: