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

Change custom build step on refactor-test-suite to treat non-consecutive test numbers as a warning #67

Open
LegalizeAdulthood opened this issue Jan 20, 2024 · 0 comments

Comments

@LegalizeAdulthood
Copy link
Owner

See bug #66 -- when trying to apply the workaround, the build will fail if the new test cases are non-consecutive in the file.

When the other bug is fixed, then test-names can treat non-consecutive test ids as an error again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant