-
Notifications
You must be signed in to change notification settings - Fork 138
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
Test full unbonding functionality in integration tests #311
Comments
Echoing the comment here I think testing this with integration tests is not a valuable use of time. It's already fairly thoroughly covered by diff tests and @MSalopek is improving that even more. |
I'm going to close for now, please reopen and justify as you see fit. |
As mentioned in the other issue, integration tests for unbonding functionality would be a sanity check that the real system works. I'm fine closing this issue so long as full unbonding is being validated in the testnet. @jtremback or @mpoke could you confirm this is the case? |
re-closing in favor of #361 |
#94 added a simple check that validator powers are changed when an
unbond
tx is submitted. We still need to test token liquidity after unbonding period has elapsed, and any anything else that's related to full unbonding hooksThis will require genesis file manipulation, see
genesisChanges
inintegration-tests/config.go
as exampleThe text was updated successfully, but these errors were encountered: