Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Cannon Go e2e tests #86

Closed
Tracked by #51
norswap opened this issue May 5, 2022 · 3 comments
Closed
Tracked by #51

Cannon Go e2e tests #86

norswap opened this issue May 5, 2022 · 3 comments
Assignees
Labels
testing Make it break
Milestone

Comments

@norswap
Copy link
Contributor

norswap commented May 5, 2022

Create e2e tests of the same kind as we have in Bedrock, in order to test L2 block validation on L2.

@norswap norswap added the testing Make it break label May 5, 2022
@norswap norswap mentioned this issue May 5, 2022
4 tasks
@norswap
Copy link
Contributor Author

norswap commented May 5, 2022

Something to consider: having some kind of transaction generator in order to have something meaningful to validate.

It seems quite hard to do well, given that we would need to deploy some smart contracts.

One possibility would be to replay some existing set of transactions from a genesis. The start of L1 mainnet history? TBD if the complexity of doing that is actually realistic.

@norswap
Copy link
Contributor Author

norswap commented May 5, 2022

The first step of this will be refactor minigeth/main.go so that it has an entry point with proper parameters and not only taking parameter specified as command line arguments / environment variables.

@norswap norswap added this to the L2-cannon milestone May 5, 2022
@protolambda
Copy link
Contributor

Cannon now runs some example Go programs, that cover the pre-image functionality that is also used by the L2 program, which is otherwise out of scope. Minigeth is no longer part of Cannon. With the op-program e2e testing we can revisit the test approach. Closing this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
testing Make it break
Projects
None yet
Development

No branches or pull requests

3 participants