You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The acceptance and E2E tests are time and cost-consuming workflows. As web projects have no impact on the validator's core implementation, we can ignore them in the mentioned test workflows. Web projects run their own independent set of tests.
Expected behavior:
When changes are pushed from web projects, the acceptance and E2E tests should not run.
Please make sure these boxes are checked before submitting your pull request - thanks!
Run the unit tests with gradle test to make sure you didn't break anything
✅ Rule acceptance tests passed.
New Errors: 0 out of 1426 datasets (~0%) are invalid due to code change, which is less than the provided threshold of 1%.
Dropped Errors: 0 out of 1426 datasets (~0%) are invalid due to code change, which is less than the provided threshold of 1%.
New Warnings: 0 out of 1426 datasets (~0%) are invalid due to code change, which is less than the provided threshold of 1%.
Dropped Warnings: 0 out of 1426 datasets (~0%) are invalid due to code change, which is less than the provided threshold of 1%.
0 out of 1426 sources (~0 %) are corrupted.
Commit: 0047f7a
Download the full acceptance test report here (report will disappear after 90 days).
✅ Rule acceptance tests passed.
Won't this change have the same issue as #1339? Namely, acceptance test are required for merging a PR, so if we exclude the workflow, you'll need a repo admin to actually merge the PR?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary:
The acceptance and E2E tests are time and cost-consuming workflows. As web projects have no impact on the validator's core implementation, we can ignore them in the mentioned test workflows. Web projects run their own independent set of tests.
Expected behavior:
When changes are pushed from
webprojects, the acceptance and E2E tests should not run.Please make sure these boxes are checked before submitting your pull request - thanks!
gradle testto make sure you didn't break anything