feat(cli): add --profile flag to report slowest tests#684
Merged
Conversation
Records each test's wall-clock duration to a temp file when --profile (or BASHUNIT_PROFILE=true) is set, then prints the slowest tests sorted descending after the summary. Count is configurable via BASHUNIT_PROFILE_COUNT (default 10). Append-only temp file aggregates correctly across the subshells spawned by parallel runs. Closes #678
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
1 participant
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.
🤔 Background
Related #678
bashunit gave no per-test timing visibility, making it hard to spot slow tests or know where to invest in speed.
💡 Changes
--profile(andBASHUNIT_PROFILE) to report the slowest tests after a run, sorted slowest-firstBASHUNIT_PROFILE_COUNT(default 10).env.example, and CHANGELOG