Ocean Bounty : Improve Unit Test Coverage for Keeper Contracts

[Anirudh2490]

Improve Unit Test Coverage for Keeper Contracts

How can you help?

We want to improve our unit test coverage, optimize integration tests and fix our test coverage generation flow for our keeper-contract repo - https://github.com/oceanprotocol/keeper-contracts/

What needs to be done?

• Optimize our existing integration tests.
• Write new unit tests. We use (truffle test)

We are very happy when

• Our unit test coverage for keeper-contracts repo is >= 85% (negotiable) indicated by our test coverage tool [solidity-coverage] (https://github.com/sc-forks/solidity-coverage).
• Our integration test coverage for keeper-contracts repo is >= 95% indicated by our test coverage tool [solidity-coverage] - (https://github.com/sc-forks/solidity-coverage).
• We have a clear separation between unit and integration tests. Unit tests should not test more than one aspect of each method at a time
• We are using truffle framework for testing (truffle test). We would prefer new tests to be written using same setup.
• PR for this implementation should go in this repo - https://github.com/oceanprotocol/keeper-contracts/

Note - We call all our existing tests as Integration tests. Unit tests will be the ones that you will implement.

Seen this problem before?

Any help solving this is welcome. Feel free to leave any comments and help someone else to solve it. We might airdrop tokens to someone even if not directly completing bounty.

Questions & Reviews

Pull requests will be reviewed by one of the maintainers or long-term contributors. In case of any additional questions feel free to ask in this thread and we will do our best to add the missing info :)

Things to know

The bounty lifecycle process including payout will be managed using Gitcoin. We'll be responding to your questions here, but for discussion and clarification we recommend to join also our Gitter channel where our tech community is accessible. In order to see the PROCN balance in your wallet you'll need to reference the related token contract with address 0xf2aabdd898a0139195b2b5da7387d43a45ded254. If you use a Metamask plugin you'll find the the exact steps here.

Reward

Once the project is reviewed and merged in the master branch, you will receive the reward. PROCN is a proto-Ocean token. Bounty hunters that earn PROCN will be able to convert them 1:1 to Ocean tokens on network launch (currently Ocean Token is valued at 0.20 EUR). Network launch is expected to happen by Mar 31, 2019. Until then PROCN will be locked and non-transferrable in the ETH wallet to which it is delivered to.

[gitcoinbot]

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

---

This issue now has a funding of 6500.0 PROCN attached to it as part of the Ocean Protocol Foundation 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
  • $57,689.83 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

Workers have applied to start work.

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

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

To begin with, I'll fix the test coverage generation. Then, I'll go through the existing test suite and work on optimisations. Once this is done, I'll start adding new tests and increase coverage.

Learn more on the Gitcoin Issue Details page.

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

The funding of 6500.0 PROCN attached to this issue has been cancelled by the bounty submitter

• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $56,241.36 more funded OSS Work available on the Gitcoin Issue Explorer

[innopreneur]

Closing this and creating a new updated bounty issue