Merged
Conversation
Add assert_duration, assert_duration_less_than and assert_duration_greater_than for verifying command execution time. Uses the framework's portable clock for cross-platform support.
Contributor
✅ Contributor ReportUser: @Chemaclass
Contributor Report evaluates based on public GitHub activity. Analysis period: 2025-02-21 to 2026-02-21 |
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.
🤔 Background
Adds assertions to verify command execution time, enabling performance testing directly in bashunit tests.
💡 Changes
assert_durationto verify a command completes within a threshold (inclusive)assert_duration_less_thanfor strict less-than duration checksassert_duration_greater_thanto verify minimum execution timebashunit::clock::nowfor cross-platform millisecond measurement