tools(e2e): register-e2e-fixtures — Phase 3 of E2E redesign#84
Merged
Conversation
…s (covers all permanent fixture domains)
Contributor
|
Dev build ready — try this branch: |
4 tasks
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.
Phase 3 of the E2E redesign per docs-internal/2026-05-02-e2e-test-suite-design.md.
Summary
tools/register-mod-fixture.ts→tools/register-e2e-fixtures.tsfoundry,cdm,hardhat,multitoE2E_DOMAINSfor Phase 4Bootstrap action (NOT run by this PR — maintainer-confirmed)
After merge, a maintainer runs once:
This registers the 4 new domains on Paseo Asset Hub. Same-owner re-publish keeps it idempotent across registry-contract redeployments (re-run as needed).
Out of scope
Test plan
bun tools/register-e2e-fixtures.ts --helpexits 0 with full fixture list