-
Notifications
You must be signed in to change notification settings - Fork 807
e2e: Switch to testnet fixture #1709
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
f8d41ab
to
6b9a223
Compare
6b9a223
to
282ed56
Compare
c32cd2c
to
a47f45a
Compare
5c01cfa
to
e10b764
Compare
04eecaa
to
bb20c3e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good few minor nits
7c85f13
to
19ccc50
Compare
Signed-off-by: marun <maru.newby@avalabs.org>
for { | ||
_, reserved := constants.NetworkIDToNetworkName[networkID] | ||
if reserved { | ||
networkID++ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All @darioush
WithTimeout(e2e.DefaultTimeout). | ||
WithPolling(e2e.DefaultPollingInterval). | ||
Should(gomega.BeTrue(), "The cluster is generating ongoing blocks. Is this test being run in parallel?") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I spent like 20m understanding how this works lol.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'm not a huge fan of how ginkgo does this but I wanted to use ginkgo for consistency. I'm writing new e2e tests with testify, and at some point we can rewrite existing tests to also use it.
Why this should be merged
This change updates the e2e test suite to use the new testnet fixture introduced in #1700. The new fixture is simpler and maintained in tree to better enable e2e test development.
As part of this change, the fixture's funded keys are allocated at-most-once to tests to avoid the following problems:
How this works
How this was tested
./scripts/tests.e2e.sh
was updated to run tests in parallel and in random order. This revealed the requirement to tag the virtuous tests asSerial
to avoid skipping on conflict with other tests../scripts/tests.e2e.persistent.sh
was updated to runtests.e2e.sh
against a persistent networkTODO