Convert Ethereum e2e into integration tests #1780
Closed
Conversation
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
sug0
force-pushed
the
tiago/ethbridge-integration-tests
branch
from
8692db2 to
836d3e1
Compare
sug0
force-pushed
the
tiago/ethbridge-integration-tests
branch
from
54c3b67 to
63a24c6
Compare
29 tasks
Collaborator
|
Not planned for now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Describe your changes
Since all Ethereum e2e tests use a single validator node, they're nice candidates to convert to integration tests, which are way more reliable, consume less resources and finish executing quicker.
Indicate on which release or other PRs this topic is based on
Currently based on #1795
Checklist before merging to
draft