test: parallelize BATS across semantic suites - #184
Merged
Conversation
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.
Summary
Why
Bats 1.13 within-file scheduling uses one-second semaphore polling, documented in KnickKnackLabs/template#7. Notes was explicitly enabling that path. Splitting by behavior gives Rush useful file-level scheduling units while keeping each test body unchanged.
All 86 test titles and bodies were mechanically verified as preserved byte-for-byte.
Validation
mise run doctorreadme build --checkgit diff --checkOne comparable local observation on exact settled main
ef2d0b19took 171.57s. The exact candidate took 135.23s, 36.34s (21.2%) faster. This is one source-supported before/after observation, not a universal benchmark.