Skip to content
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.

Sign up for GitHub

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

Jump to bottom

System tests for KEEP<>T staking contracts interactions #33

Merged
merged 7 commits into from
Dec 20, 2021
Merged

System tests for KEEP<>T staking contracts interactions #33

merged 7 commits into from
Dec 20, 2021

Commits on Nov 17, 2021

  1. KEEP<>T delegate stake system tests 

    The following scenarios are tested:

1. Given I am KEEP network managed grant staker and I have not
undelegated my stake, when I authorize T staking contract,
I can copy my delegation to T staking contract.

2. Given I am KEEP network managed grant staker and I have
undelegated my stake, when I authorize T staking contract,
I can not copy my delegation to T staking contract.

3. Given I am KEEP network non-managed grant staker and
I have not undelegated my stake, when I authorize T staking
contract, I can copy my delegation to T staking contract.

4. Given I am KEEP network non-managed grant staker and
I have undelegated my stake, when I authorize T staking
contract, I can not copy my delegation to T staking contract.

5. Given I am KEEP network liquid token staker and I have not
undelegated my stake, when I authorize T staking contract,
I can copy my delegation to T staking contract.

6. Given I am KEEP network liquid token staker and I have
undelegated my stake, when I authorize T staking contract,
I can not copy my delegation to T staking contract.
    @pdyraga
    pdyraga committed Nov 17, 2021
    Configuration menu
    Copy the full SHA
    3a79bad View commit details
    Browse the repository at this point in the history

  2. KEEP<>T top-up stake system tests 

    The following scenarios are tested:

1. Given I am KEEP network liquid token staker and I copied my stake to T
staking contract, when I executed top-up of my legacy stake,
`topUpKeep` should top-up my stake in T staking contract.

2. Given I am KEEP network non-managed grant staker and I copied my stake to T
staking contract, when I executed top-up of my legacy stake,
`topUpKeep` should top-up my stake in T staking contract.

3. Given I am KEEP network managed grant staker and I copied my stake to T
staking contract, when I executed top-up of my legacy stake,
`topUpKeep` should top-up my stake in T staking contract.
    @pdyraga
    pdyraga committed Nov 17, 2021
    Configuration menu
    Copy the full SHA
    7e80a1b View commit details
    Browse the repository at this point in the history

  3. Use real-world token amounts in system tests

    @pdyraga
    pdyraga committed Nov 17, 2021
    Configuration menu
    Copy the full SHA
    8504713 View commit details
    Browse the repository at this point in the history

  4. KEEP<>T undelegate system tests 

    The following scenarios are tested:

1. Given I am KEEP network liquid token staker, when I copied my stake to
T staking contract, when I authorized and deauthorized application,
`unstakeKeep` should release and let me undelegate my KEEP stake.

2. Given I am KEEP network managed grant staker, when I copied my stake to
T staking contract, when I authorized and deauthorized application,
`unstakeKeep` should release and let me undelegate my KEEP stake.

3. Given I am KEEP network non-managed grant staker, when I copied my stake to
T staking contract, when I authorized and deauthorized application,
`unstakeKeep` should release and let me undelegate my KEEP stake.
    @pdyraga
    pdyraga committed Nov 17, 2021
    Configuration menu
    Copy the full SHA
    5bd37e6 View commit details
    Browse the repository at this point in the history

  5. KEEP<>T slashing/seizing system tests 

    The following scenarios are tested:

1. Given I am KEEP network liquid token staker, when I copied my stake to
T staking contract, when I authorized application, when I got slashed by
the application, `processSlashing` should slash my KEEP stake.

2. Given I am KEEP network liquid token staker, when I copied my stake to
T staking contract, when I authorized application, when I got slashed by
the application, `notifyKeepStakeDiscrepancy` should revert.

3. Given I am KEEP network liquid token staker, when I copied my stake to
T staking contract, when I authorized application, when the application
seized my stake, `processSlashing` should seize my KEEP stake.

4. Given I am KEEP network liquid token staker, when I copied my stake to
T staking contract, when I authorized application, when the application
seized my stake, `notifyKeepStakeDiscrepancy` should revert.

5. Given I am KEEP network managed grant staker, when I copied my stake to
T staking contract, when I authorized application, when I got slashed by
the application, `processSlashing` should slash my KEEP stake.

6. Given I am KEEP network managed grant staker, when I copied my stake to
T staking contract, when I authorized application, when I got slashed by
the application, `notifyKeepStakeDiscrepancy` should revert.

7. Given I am KEEP network managed grant staker, when I copied my stake to
T staking contract, when I authorized application, when the application
seized my stake, `processSlashing` should seize my KEEP stake.

8. Given I am KEEP network managed grant staker, when I copied my stake to
T staking contract, when I authorized application, when the application
seized my stake, `notifyKeepStakeDiscrepancy` should revert.

9. Given I am KEEP network non-managed grant staker, when I copied my stake to
T staking contract, when I authorized application, when I got slashed by
the application, `processSlashing` should slash my KEEP stake.

10. Given I am KEEP network non-managed grant staker, when I copied my stake to
T staking contract, when I authorized application, when I got slashed by
the application, `notifyKeepStakeDiscrepancy` should revert.

11. Given I am KEEP network non-managed grant staker, when I copied my stake to
T staking contract, when I authorized application, when the application
seized my stake, `processSlashing` should seize my KEEP stake.

12. Given I am KEEP network non-managed grant staker, when I copied my stake to
T staking contract, when I authorized application, when the application
seized my stake, `notifyKeepStakeDiscrepancy` should revert.
    @pdyraga
    pdyraga committed Nov 17, 2021
    Configuration menu
    Copy the full SHA
    965140e View commit details
    Browse the repository at this point in the history

Commits on Dec 20, 2021

  1. Merge branch 'main' into system-tests

    @nkuba
    nkuba authored Dec 20, 2021
    Configuration menu
    Copy the full SHA
    89099e0 View commit details
    Browse the repository at this point in the history

  2. Explained token supplies in test init contracts script

    @pdyraga
    pdyraga committed Dec 20, 2021
    Configuration menu
    Copy the full SHA
    bb5e4a3 View commit details
    Browse the repository at this point in the history