Skip to content
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

Run tests on the built binary at some point before release. #19411

Closed
jennifer-shehane opened this issue Dec 17, 2021 · 1 comment
Closed

Run tests on the built binary at some point before release. #19411

jennifer-shehane opened this issue Dec 17, 2021 · 1 comment
Labels
process: tests Related to our internal tests type: chore Work is required w/ no deliverable to end user

Comments

@jennifer-shehane
Copy link
Member

What would you like?

We are not running the entirety of our test suites/examples against the binary version of Cypress after it is built. We had a recent regression that would have been caught by this type of testing.

This is not a gamut of tests that should be run on every commit in PRs or even on every commit into develop as it would be prohibitively slow to our own testing suite (they would have to run after the build binary steps), but it's something that could be run before our next release (nightly/weekly/manually at release time).

Why is this needed?

No response

Other

No response

@jennifer-shehane jennifer-shehane added process: tests Related to our internal tests type: chore Work is required w/ no deliverable to end user labels Dec 17, 2021
@jennifer-shehane
Copy link
Member Author

Closing as this has already been addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
process: tests Related to our internal tests type: chore Work is required w/ no deliverable to end user
Projects
None yet
Development

No branches or pull requests

1 participant