Add code coverage - #504
Conversation
|
hola @solegalli, I created the Two questions:
|
|
hi @Morgan-Sell to be honest I have not used code coverage before, so I need to do some research to answer those questions. In short, I don't know :_( |
|
Hi @solegalli, For our current needs, I believe the two main sections are
You can exclude lines introducing blocks, and the entire block is excluded. If you exclude a def line or decorator line, the entire function is excluded. Be careful when writing this setting: the values are regular expressions that only have to match a portion of the line. For example, if you write ..., you’ll exclude any line with three or more of any character. If you write pass, you’ll also exclude the line my_pass="foo", and so on. Here's imbalanced-learn .coveragerc. With imbalanced-learn, I think using |
Code coverage will allow us to measure how much of the feature-engine source code is tested.
Closes #323.
Notes from #323:
At the moment, we have no visibility of test coverage. I would like to include this in the package.
Here some useful links I gathered:
https://gist.github.com/dnozay/5b9b818ff0dc857d1358
https://pytest-cov.readthedocs.io/en/latest/tox.html
https://coverage.readthedocs.io/en/6.1.1/config.html
Also check imbalanced-learn package, they have some code to run coverage.