added codecov support

[shubhank-saxena]

This fixes #640
We still need to register the repo on codecov so that the test coverage can be picked up!
@vringar

[vringar]

Why is this line still here, did we use to have codecov enabled before?
And why should we do it differently now than we did before?

[shubhank-saxena]

That's something I missed 😮

[shubhank-saxena]

I followed up using npm. Can be done this way too

[vringar]

Thanks for submitting this PR.
There are a couple of points that are still unclear to me only some of which can be addressed by you:

• Who do I need to talk to, to get this enabled for us? (That's probably a task for me)
• Shouldn't these tools be in requirements-dev.in and package.json respectively?
• Do we want to create policies around this tool (e.g. no lowering the code coverage) or is it just informative

[shubhank-saxena]

• We can add them in the respective requirement files. But codecov only runs just on the Travis. So this way it won't clutter the packages. If you want, I can shift them.
• Currently, this is informative only. Can be toggled to a policy if and when required (like a threshold that every PR should at least maintain 40%+ coverage and shouldn't dip it

[birdsarah]

We can add them in the respective requirement files. But codecov only runs just on the Travis. So this way it won't clutter the packages. If you want, I can shift them.

I think we should include in dev requirements. It's small and it makes sure everywhere's working with the same set of dependencies which makes it easier to track down problems.

The rebase now #648 is in will probably be a bit gross. Apologies. You may just want to start a new branch. The good news is the PR will be smaller as .travis.yml shrunk considerably.

[shubhank-saxena]

@birdsarah sure! Will start a new PR! #648 is literally a great thing! 🚀