-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CX_HARDENING] Enhance DA Task Test Coverage #3568
Open
shamb0
wants to merge
5
commits into
EspressoSystems:main
Choose a base branch
from
shamb0:shamb0/cxh-improve-DATask-test-coverage
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
5023e59
[CX_HARDENING] Enhance DA Task Test Coverage
shamb0 3cb4bc0
Refactor: Address review comments
shamb0 8411537
Merge remote-tracking branch 'upstream/main' into shamb0/cxh-improve-…
shamb0 02a3d4d
Refactor: Address review comments
shamb0 dfacef7
Merge remote-tracking branch 'upstream/main' into shamb0/cxh-improve-…
shamb0 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm hesitant to make such a specific change for the tests in this case, especially since you have them working and debugging is not as big of an issue at this point. While it's not ideal to spin up the entire SystemContext for unit tests, this method unfortunately creates a rift in what is the accepted testing framework, and what is done here. If we made this change, we'd want to propagate it to all tests, lest we end up in the situation where specific knowledge of this specific suite rests solely with someone who is not on the team.
I am not opposed to the outright removal of this in theory, though I think for this PR, we should stick to the existing spawner.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jparr721, I understand your concerns about consistency in our testing framework. To clarify, the existing
hotshot-testing::helpers::build_system_handle()
function remains unchanged, and all current test cases continue to work as expected.The new API,
hotshot-testing::helpers::build_system_handle_from_launcher()
, was added to address issue #3160, which requires 'Permute the inputs and verify if the tests still pass.'. Whilebuild_system_handle()
uses default test configuration parameters, the new function provides flexibility by allowing modifications to the setup.I suggest we review its usage in the test scenarios. If it doesn’t add significant value, we can consider removing it. Specifically,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not just use the
random!
macro to get permuted inputs in that case? Furthermore, we do handle the vote collection and DA votes within the integration tests (e.g.test_success
), so spinning up additional nodes for those might not be explicitly necessary.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @jparr721, for your suggestion. I agree that utilizing random!() could be an effective way to introduce fuzziness in test configuration parameters. I will explore this approach and provide an update on the outcome.