Write and Test - Truffle Tests for Smart Contracts, on Forked Mainnet

[amateur-dev]

Objective: This Bounty is for stress testing the zUniPool Contract, using, Truffle test and Forked Mainnet.

Please go through the ReadMe in detail.

Once you have written the complete Test Script, please submit it as a PR.

Scope of the test: The Scope of the test should cover, the following, at least:

1. First user is able to stake LP tokens at a price of 1:1
2. Second user is also able to stake LP, immediately, at a price of 1:1
3. Immediately, the First User is able to withdraw its LP with the same number of LP tokens
4. Immediately, the Second User is able to check the value of its zUNI tokens and it should return, at least, the same number of LP tokens that it staked (or higher)
5. Third User is able to stake LP tokens, after a week of time lapse, but the zUNI Tokens issued to the Third User is not at a price ratio of 1:1, but lesser number of zUNI Tokens compared to the number of LP tokens staked
6. At the same time, Second User wants to burn [ getMyStakeOut ] a exactly half of its zUNI Tokens, and it is able to receive LP tokens.
   • The LP tokens received at this stage by Second User is higher than half of the LP Tokens staked by the Second User

Goal: One should be able to run truffle test test/name_of_the_script, testing on a ganache testnet, which is run by using the ganache-cli —fork

Note: For the purpose of this test, you will be required to acquire LP tokens. You could do so, {in the forked mainnnet}, by calling the function LetsInvest(address _TokenContractAddress, address _towhomtoissue) in the UnipoolGeneralZap Smart Contract, running on the mainnet at 0x97402249515994Cc0D22092D3375033Ad0ea438A.

Additional Token Information, for ease of reference:

sETH Token Address: 0x5e74c9036fb86bd7ecdcb084a0673efc32ea31cb

sETH_LP_Address: 0xe9Cf7887b93150D4F2Da7dFc6D502B216438F244

Original UniPool: 0x48D7f315feDcaD332F68aafa017c7C158BC54760 {the contract developed and deployed by Synthetix Team}

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 400.0 DAI (400.0 USD @ $1.0/DAI) attached to it as part of the @DeFiStrategies fund.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $78,925.15 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work has been started.

These users each claimed they can complete the work by 1 year, 11 months ago.
Please review their action plans below:

1) pbteja1998 has applied to start work (Funders only: approve worker | reject worker).

I will write tests based on the requirements given. Then acquire LP tokens and then will test accordingly. I have previously done bounties related to testing smart contracts.
2) bobface has been approved to start work.

I have written lots of contract unit tests in the past and am familiar with liquidity pools. I have completed bounties to deploy custom forks of Uniswap in the past. This way I will be able to quickly understand the contract source and test it appropriately. Thanks for considering me!
3) mds1 has been approved to start work.

Hey there! This seems like a straightforward task and a clear description, so I should be able to get this done for you pretty quickly.

I have a lot of experience testing against the forked mainnet—most recently with the Floatify contracts the FakerDAO contracts—so am familiar with its features and quirks. I can also add in a few events for you, since it seems the LPTokensStaked and LPTokensWithdrawn events are currently not used.
4) ridesolo has been approved to start work.

Hello, I have worked any many staking algorithms and tests units, you can check below to confirm my experience:
https://github.com/EthereumCommonwealth/Governance-System/tree/master/staking_contract
https://github.com/callisto-staking
https://github.com/staking-library
I also created a recent grant related with staking algorithm as you can see here https://gitcoin.co/grants/470/staking-library?tab=description.
Also as expert solidity auditor https//gist.github.com/ridesolo, I will try to write complete test to avoid any possible issues.
The work plan is quiet clear, so I will do my best to make it quickly.

Learn more on the Gitcoin Issue Details page.

[gitcoinbot]

@iamonuwa Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[iamonuwa]

@gitcoinbot, work in progress. Sending in PR.

[gitcoinbot]

@Bobface Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[Bobface]

@gitcoinbot I'm on it

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work for 400.0 DAI (400.0 USD @ $1.0/DAI) has been submitted by:

1. @bobface

@nodar please take a look at the submitted work:

• PR by @Bobface

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $80,752.21 more funded OSS Work available on the Gitcoin Issue Explorer

[RideSolo]

thanks for approving my request, I will submit the tests asap.

[Bobface]

Hey @amateur-dev I opened a PR days ago with the tests.

[mds1]

@amateur-dev @nodar Looks like a PR was submitted about a week ago, but also saw that there were two new approvals to start work—just want to double-check those approvals were intentional before starting anything. Thanks!

[RideSolo]

I think that he meant to create a "contest" project type probably, @nodar can you please confirm

[Solexplorer]

Hey @amateur-dev,
Solexplorer from Gitcoin here, I see that @Bobface has already created a PR, did you get a chance to look on it and provide him with feedback if you have any?

Looking forward to your reply

[amateur-dev]

@RideSolo apologies for the delay in responding. I was away from desk and COVID has not been kind. We did not intend to create a "contest" but sadly, we have did not yet get someone to give us the proper test set up in which we (a) either know what the issue is, or (b) there is no issue at all. So we are still looking for the right PR. cc: @mds1

[RideSolo]

@amateur-dev no problem we can all understand the situation, just let us know if you don't solve it with Bobface, so we start working on it (me or mds1)

[nodar]

Hey @Bobface let us know if you are still interested in helping out on this. Thank you for checking in guys, just noticed these. @RideSolo @mds1