-
Notifications
You must be signed in to change notification settings - Fork 0
Restore version upgrade tests #18
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
base: master
Are you sure you want to change the base?
Conversation
|
PASS [ 43.556s] (3/3) lit_node::test toxiproxy::perf_tests::load_with_no_latency |
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.
Pull request overview
This PR restores previously commented-out version upgrade tests by refactoring them to use the standardized TestSetupBuilder pattern instead of manual test setup code.
- Refactored three version upgrade tests to use
TestSetupBuilderfor cleaner, more consistent test initialization - Removed manual contract and validator setup boilerplate code
- Updated
NetworkIntegrityCheckerinstantiation to use the new API signature requiring bothend_userandactionsparameters
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
rust/lit-node/lit-node/tests/upgrades/version_upgrades.rs |
Refactored three version upgrade tests to use TestSetupBuilder, removed manual setup code, updated API calls, but missing custom_binary_path usage for the third test |
rust/lit-node/lit-node/tests/test.rs |
Re-enabled the upgrades test module by uncommenting it |
rust/lit-node/lit-node/src/git_info.rs |
Updated git commit hash to reflect current commit |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Pull request overview
This PR restores previously commented-out version upgrade tests by refactoring them to use the standardized
TestSetupBuilderpattern instead of manual test setup code.TestSetupBuilderfor cleaner, more consistent test initializationNetworkIntegrityCheckerinstantiation to use the new API signature requiring bothend_userandactionsparametersWARNING !
The main test now proves that code is backwards compatible to a given branch/release.. It does NOT prove that a particular methodology for upgrading nodes work - outside of deploying new nodes with new stakers and dealing them in, while dealing out old nodes.