Web: Increase Code Coverage by 4%

Created on 1 Feb 2018 · 12Comments · Source: gitcoinco/web

This bounty will be paid out to anyone who meaningfully increases the code coverage of the repository by 4%.

Criteria:

You must increase the code coverage (as measured by codecov) of this repo by 4%.
You must put (show) some thought into success / failure criteria for each method tested.
Please coordinate with other bounty hunters who are working on this bounty so you don't overlap work.

Source

owocki

🎉1

All 12 comments

__This issue now has a funding of 0.055 ETH (61.14 USD) attached to it.__

If you would like to work on this issue you can claim it here.
If you've completed this issue and want to claim the bounty you can do so here
Questions? Get help on the Gitcoin Slack
$12274.5 more Funded OSS Work Available at: https://gitcoin.co/explorer

gitcoinbot on 1 Feb 2018

__Work has been started on the 0.055 ETH (58.02 USD) funding by__:

@tyleryasaka

__Please work together__ and coordinate delivery of the issue scope. Gitcoin doesn't know enough about everyones skillsets / free time to say who should work on what, but we trust that the community is smart and well-intentioned enough to work together. As a general rule; if you start work first, youll be at the top of the above list ^^, and should have 'dibs' as long as you follow through.

On the above list? Please leave a comment to let the funder (@owocki) and the other parties involved what you're working, with respect to this issue and your plans to resolve it. If you don't leave a comment, the funder may expire your submission at their discretion.

Learn more on the gitcoin issue page
Questions? Get help on the Gitcoin Slack
$11678.19 more Funded OSS Work Available at: https://gitcoin.co/explorer

gitcoinbot on 1 Feb 2018

@owocki This'll be my first time working with this repo, and using codecov for that matter. I've got plenty of experience writing tests so I expect I can figure it out, but I'll post an update if I get stuck on anything.

tyleryasaka on 1 Feb 2018

🎉1

@tyleryasaka Thanks for picking this up! Feel free to let me know if you have any questions. Just a note, we're using pytest on Travis.

Looking forward to seeing coverage go up!

mbeacom on 2 Feb 2018

👍1

@mbeacom Thanks! I do have one question. I think you guys might have a team yaml set up for codecov, because when I run it I get a much different number - and I don't see any codecov configurations in the repo. Is there a way I could view the team yaml so I can know what percentage I'm at? 😃

EDIT: I ended up just creating a PR which is the easiest way to get the codecov report. I would still be curious what about the team yaml but it's not necessary.

tyleryasaka on 3 Feb 2018

__Work for 0.055 ETH (45.52 USD) has been submitted by @tyleryasaka.__

@tyleryasaka, please leave a comment to let the funder (@owocki) (and the other parties involved) that you've submitted you work. If you don't leave a comment, the funder may expire your submission at their discretion.