#87 Make latency_ms assertion deterministic by mocking perf_counter - #101
Merged
deyna256 merged 2 commits intoMar 3, 2026
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
2 participants
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.
This PR makes the latency_ms assertion in
test_generate_success_returns_content_and_metricsdeterministic.Previously, the test only asserted
metrics.latency_ms > 0, which always passes becausetime.perf_counter()was not mocked. This did not verify that latency was computed correctly.The test now mocks
time.perf_counter()to control start and end times, allowing assertion of the exact expected latency value in milliseconds.All test case passed @deyna256
Resolve #87