Fix codecov

[WisdomPill]

Just have a look at the readme, there is the codecov badge but the tests are not setup for coverage

[krishp058]

But what specifically do you want me to do?

[WisdomPill]

Codecov does not get coverage sent to it after the tests, as a matter of fact if I remember correctly coverage does not even run. Let's close #506 first and then you could work on it so that we do not step on each other feet

[WisdomPill]

Basically we need to switch to pytest and use pytest-cov.

It could be difficult, probably it is not a "good first issue", @krishp058 do you still want to give it a try or I could step in and fix it.

Here is the "tutorial" by codecov.

[krishp058]

Oh sorry about the late response, I think it should be best if you can do this because I'm not very well familiar with codecov and also I'm still a beginner so I was looking from something that would match my skillset. But I really appreciate you trying to give me a chance.

Thanks

[WisdomPill]

@terencehonles let's talk coverage and whether to switch to pytest or not.

I have tried locally to use coverage.py it seems to work, but I don't know how to make it work with tox.
Another thing is that the tests are launched separately so code coverage will not hit some clients or serializers in now run as of now.

Do you have any proposals, I remember you talked about switching to pytest previously

[terencehonles]

I think I figured out what we need to do to cover it all. I'll take care of this.

My current thoughts: Instead of creating N test runners with different settings use pytest and one runner and use fixtures to stub out the different CACHES.

[terencehonles]

Sadly I had forgotten that the fixture parametrization I was thinking to use would not work with unittest style test cases. We'll probably want to migrate off of those, but for now running pytest multiple times and appending to the coverage file should be fine.