pytest-cov
pytest-cov copied to clipboard
Coverage plugin for pytest.
In continuation of https://github.com/pytest-dev/pytest-cov/issues/379: @nedbat I am facing same issue on Windows, Python 3.6.4. .pybuilder\plugins\cpython-3.6.0.final.0\lib\site-packages\coverage\sqldata.py", line 1048, in execute INTERNALERROR> return self.con.execute(sql, parameters) INTERNALERROR> **sqlite3.OperationalError: Safety level may not be...
# Summary I am building out a testing framework, and as part of it I'm building fixtures on classes that inherit at various levels. For example: a BaseTest class that...
Hello, I'm a beginner user of pytest-cov, and i'm having a problem when i run the command `pytest --cov=app`. Expected result When i run this command, my expected result is...
# Summary When I run `coverage` directly I get a sensible report showing a coverage of my module at 83%: ```shell $ cat .coveragerc [run] source = turbot omit =...
Similar to `--omit` option in [coverage.py](https://coverage.readthedocs.io/en/latest/source.html#execution), this option could be used to ignore some specific files. Ignoring files can be done with a `.coveragerc` file, but many developers don't want...
Example where pytest-cov produces console spam: when you call `pytest --collect-only`. Obviously that doing a coverage report when you do not run even one test makes no sense. Also when...
As described [in StackOverflow](https://stackoverflow.com/questions/61112438/wrong-coverage-report-with-webtest) I have simple WebApp that I am testing with WebTest but the coverage result report missed lines that are executed. This might be related to #117...
# Summary I am trying to get a coverage report with definition lines included, when invoke pytest and pytest-cov from Python code directly. It is more convenience, compare with cmd...
I am using python 3.7.1, pytest 4.6.3 and pytest-cov 2.8.1 and my .coveragerc file contains parallel set to true. With the above configuration when i run tests in parallel It...
# Summary I have series of tests where the assertion needs to be executed inside of a closure (nested) test function since it needs to utilize a separate test framework...