-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Testing] Supplier staking E2E test #498
Conversation
The CI will now also run the e2e tests on devnet, which increases the time it takes to complete all CI checks. If you just created a pull request, you might need to push another commit to produce a container image DevNet can utilize to spin up infrastructure. You can use |
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.
Left a couple of comments but nothing blocking 👍
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.
Love it!
I want this to add gateways to it.
…cept * pokt/main: [Dashboard] Supplier logs dashboard (#502) [Utility] Update SessionSettlement when app goes into a negative amount (#509) [Testing] Supplier staking E2E test (#498) [RelayMiner] Support https backend urls (#507) [Bug] Fix pprof endpoint (#505) [LocalNet] Remove tilt-restart-wrapper (#504) [LocalNet][Hotfix] Turn off pproff by default (#500) [Tooling] Add pprof endpoints and documentation (#484) [Documentation] Basic blockchain operations (#454) [BlockClient] Refactor BlockClient to fetch latest block at init (#444)
Summary
E2E Tests for staking the supplier:
make test_e2e_supplier
Issue
Type of change
Select one or more:
Testing
Local Testing (only if making code changes)
make go_develop_and_test
make test_e2e
PR Testing (only if making code changes)
devnet-test-e2e
label to the PR.make trigger_ci
if you want to re-trigger tests without any code changes