migrate chaos tests to e2e/chaos package and V3 RunScenario#1226
Draft
Farber98 wants to merge 2 commits into
Draft
migrate chaos tests to e2e/chaos package and V3 RunScenario#1226Farber98 wants to merge 2 commits into
Farber98 wants to merge 2 commits into
Conversation
Extract Pumba outage helpers and container resolution from chaos_test.go into build/devenv/tests/e2e/chaos so cross-family e2e can reuse them without duplicating Pumba or cfg lookup logic
Add RunScenario pipeline (SendV3Message, assert, ConfirmExecOnDest) and refactor all TestChaos_* tests off runV2TestCase. FamilyEVM filter moves to test call site; chaos package stays family-agnostic for cross-chain reuse.
Farber98
changed the title
|
Code coverage report:
|
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
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.
Why
Chaos e2e tests embedded
Pumbacommands, container lookup, and a V2 send/assert path directly inchaos_test.go. That was fine for EVM-only, but now we need chaos tests in other families and avoid copying all primitives and setup. (eg.Pumba, env-out parsing, etc.)This PR extracts shared chaos helpers and migrates all
TestChaos_*tests onto a single V3 scenario runner.What
New
e2e/chaos/package:Pumba(InjectOutage, duration constants)ccv.Cfg(aggregator nginx, verifiers, executors, indexer)ExecutorContainersForDestfor dest-chain executor targeting (needed when multiple executors share the same qualifier)HydrateEVMEOADefaultVerifierfor EVM chaos message setupchaos_test.go refactor:
TestChaos_*tests useRunScenario(norunV2TestCase, no inlinePumba)setupChaosno longer loads chains or filters by family; EVM lib loading stays at the test call sitetcapi.AssertMessageOptionsand the V3 message pipeline