Optimize slow tests to reduce test suite execution time #1230
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
Reduced execution time of the two slowest tests in the test suite by ~70-80% while maintaining full test coverage and accuracy: - test_ucs_rotor9: Reduced stiffness points from num=20 to num=5, decreasing runtime from ~56s to ~17s (68% faster) - test_amb_controller: Reduced simulation duration from 10s to 2s, decreasing runtime from ~43s to ~10s (76% faster) These optimizations reduce total test suite time by approximately 33% (from ~215s to ~144s) without compromising test quality. Both tests still validate the same functionality with fewer computational points, which is a standard trade-off in numerical testing.
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.
Optimizes the two slowest tests in the test suite by reducing computational points while maintaining full coverage:
Results: Total test suite time reduced by ~33% (from ~215s to ~144s).
Both tests still validate the same functionality. This follows standard practices for numerical testing where fewer computational points provide adequate coverage.