-
Notifications
You must be signed in to change notification settings - Fork 36
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
Update system tests #647
Update system tests #647
Conversation
Looks like we have a system test failure: https://github.com/keep-network/tbtc-v2/actions/runs/5484145856 |
I ran this workflow before bumping the |
Request the redemption via the `depositorBridgeHandle.requestRedemption` directly instead of `requestRedemption` function. After refactoring in `#632`, the `requestRedemption` requests redemption via tBTC token contract. In the current deposit scenario, we do not pass the vault address so the `depositor` does not actually have any tBTC tokens so we can't request redemption via `requestRedemption` fn with changes from `#632`. We are going to add a new scenario where we pass the TBTC vault address to the `revealDeposit` function to test the new mechanism of requesting the redemption via tBTC token contract in follow-up work.
ee3cab1
to
b56d4db
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.
LGTM! Will merge once https://github.com/keep-network/tbtc-v2/actions/runs/5529864532 turns green!
This PR adds additional system tests scenario in which deposit is revealed with a vault. This PR is a follow-up to #647. In the already existing scenario, the depositor revealed their deposit without specifying the vault. As a result the depositor had their blance increased in the Bank. In the new scenario the depositor reveals their deposit and provides the vault address. As a result TBTC tokens are minted for the depositor.
Request the redemption via the
depositorBridgeHandle.requestRedemption
directly instead of
requestRedemption
function. After refactoring in#632, the
requestRedemption
requests redemption via tBTC tokencontract. In the current deposit scenario, we do not pass the vault
address so the
depositor
does not actually have any tBTC tokens so wecan't request redemption via
requestRedemption
fn with changes from#632. We are going to add a new scenario where we pass the TBTC vault
address to the
revealDeposit
function to test the new mechanism ofrequesting the redemption via tBTC token contract in follow-up work.