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

Fix no valid test when sharding #268

Merged
merged 8 commits into from
Oct 25, 2024
Merged

Conversation

fellen31
Copy link
Contributor

  • Closes No valid tests when using --shard and --changed-since #267, by moving the testSuits.isEmpty() check so that shards with no tests do not result in an error.
  • Clarifies the distinction between files with tests and the total number of tests within the files. E.g., so that one file containing with two tests aligns with the final Executed 1 tests. 1 tests failed. Done! message.
  • Fixes a java.lang.IllegalArgumentException: Input list cannot be null or empty when running with a nonexistent tag (resulting in no tests) together with sharding.

@sateeshperi
Copy link
Contributor

sateeshperi commented Oct 25, 2024

ah this makes sense now, saw this error just today and was perplexed about it.

Thanks for reporting and putting in a fix @fellen31

@lukfor lukfor merged commit 74a283f into askimed:main Oct 25, 2024
6 checks passed
@lukfor
Copy link
Collaborator

lukfor commented Oct 25, 2024

Thank you Felix! 🙏🚀

@nvnieuwk
Copy link
Contributor

nvnieuwk commented Nov 4, 2024

Any idea on when this will be in a release? 😁

@lukfor
Copy link
Collaborator

lukfor commented Nov 4, 2024

Tomorrow 🙌

@lukfor
Copy link
Collaborator

lukfor commented Nov 4, 2024

Done 🚀

@nvnieuwk
Copy link
Contributor

nvnieuwk commented Nov 5, 2024

Awesome, thank you!

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

Successfully merging this pull request may close these issues.

No valid tests when using --shard and --changed-since
4 participants