How to do end-to-end test of permissioned deployment?

[dckc]

@ivanlei asked for some details around extending the docker-based upgrade-test framework for end-to-end testing of permissioned deployment.

[dckc]

@anilhelvaci , as we discussed, 53:kread-start in agoric-3-proposals is a good template now.

Note the docs on Naming:

Each proposal is defined as a subdirectory of propoals. E.g. 16:upgrade-8. The leading number is its number as submitted to the agoric-3 chain. ... If the proposal is pending and does not yet have a number, use a letter.

[dckc]

@turadg and @mhofman are presenting agoric-3-proposals tooling that makes this pretty straightforward.
Here's hoping for a bit of explanation here or linked from here.

[turadg]

https://github.com/Agoric/agoric-3-proposals has docs. https://github.com/Agoric/agoric-3-proposals/tree/main/packages/synthetic-chain too

[dckc]

Adding an analog to https://github.com/Agoric/agoric-sdk/tree/master/a3p-integration looks like a best practice for MN2 dapps, based on discussion with @mhofman and @Chris-Hibbert

Here's hoping we find time to elaborate a bit more on this.

cc @Jovonni

[dckc]

dapp-offer-up and dapp-agoric-basics have end-to-end deployment testing now.

In some cases, it includes testing all the way out to the web UI.

• https://github.com/Agoric/dapp-offer-up/blob/main/.github/workflows/pr.yml#L27
• https://github.com/Agoric/dapp-offer-up/actions/runs/10523555796/job/29158478024

for high level discussion:

• Agoric/Synpress: A Custom E2E Testing Framework for Cosmos SDK

end-to-end testing of dapp-orchestration-basics involves not just one chain running in docker, but several. Landing that is just around the corner:

• [WIP] orchestration-basics now uses multichain-testing for end-to-end tests dapp-orchestration-basics#32