You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From Lasse:
One of the really nice testing features to have for the sandbox would be reverting the state back to a certain snapshot.
With the snapshotted trees (and also use snapshots of the anvil state), we should be able to send a command that "rollback" to the specified snapshot (both L1 and L2 state).
This could be used to heavily reduce testing times where there is a lot of repetitive setup. As you would just do a snapshot in beforeEach and a cheatcode.rollback() in the afterEach().
For tests that are going back and deploying the full setup at every single iteration this should be a massive speedup.
Definition of Done:
e2e tests use these to speed them up
In process of doing so, we might end up creating methods to easily use the snapshot tree. This should be documented - Seek devrel's help for this
The text was updated successfully, but these errors were encountered:
LHerskind
changed the title
Expose Snapshot tree for sandbox tests + use in e2e tests
feat(Snapshot): Expose Snapshot tree for sandbox tests + use in e2e tests
Mar 9, 2024
From Lasse:
One of the really nice testing features to have for the sandbox would be reverting the state back to a certain snapshot.
With the snapshotted trees (and also use snapshots of the anvil state), we should be able to send a command that "rollback" to the specified snapshot (both L1 and L2 state).
This could be used to heavily reduce testing times where there is a lot of repetitive setup. As you would just do a snapshot in
beforeEach
and acheatcode.rollback()
in theafterEach()
.For tests that are going back and deploying the full setup at every single iteration this should be a massive speedup.
Definition of Done:
The text was updated successfully, but these errors were encountered: