Repository navigation
Skip execution for empty test shards - #2041
Merged
Merged
Conversation
This was referenced Nov 18, 2026
1 of 2 tasks
Member
|
Thanks! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Description
When a shard has no assigned tests, Pest forwards the original arguments and can run the entire selection while reporting that zero files ran.
Apply a filter that matches no tests to an empty shard. This keeps the existing empty-suite exit policy in serial and parallel runs and makes
--list-testsshow the shard's selection.Added CLI tests for both runners,
--fail-on-empty-test-suite, and listing. The shard test suite also passes with the changes from #1829 applied locally. That PR changes how tests are assigned to shards.