-
Notifications
You must be signed in to change notification settings - Fork 5
[Feature] Add integration test for Orbit chain deployment workflow #25
Copy link
Copy link
Open
Labels
enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomers
Description
Is this related to a problem?
M4 Orbit tools work independently but there's no test that verifies the full deployment workflow end-to-end: config → deployment → validator setup. If one tool's output format changes, dependent tools might break silently.
Describe the feature
Create tests/mcp_tools/test_orbit_e2e.py with an integration test that:
- Generates an Orbit chain config (Rollup mode)
- Passes config output to deployment generation
- Passes deployment output to validator setup
- Verifies all outputs are structurally valid and reference each other correctly
- Repeat for AnyTrust mode
Which module does this relate to?
- M4: Orbit (chain config, deployment, validators)
Example usage
def test_full_orbit_rollup_workflow():
# Step 1: Generate config
config_result = generate_orbit_config.execute({"chain_type": "rollup", ...})
assert "prepareChainConfig" in config_result["code"]
# Step 2: Generate deployment using config
deploy_result = generate_orbit_deployment.execute({"chain_type": "rollup", ...})
assert "createRollup" in deploy_result["code"]
# Step 3: Generate validator setup
validator_result = generate_validator_setup.execute({"setup_type": "validator", ...})
assert "docker-compose" in str(validator_result)Additional context
- Follow the pattern in
tests/mcp_tools/test_m2_e2e.pyif it exists - Test both Rollup and AnyTrust modes
- Files:
src/mcp/tools/generate_orbit_*.py,src/templates/orbit_templates.py
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomers