Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
platform specific configuration
See original GitHub issueOriginally reported by John Vandenberg (Bitbucket: jayvdb, GitHub: jayvdb)
If a block has two platform/OS-specific branches, currently the only way to reach 100% with a single configuration is to use #pragma: no cover on both branches, ignoring the block when coverage is run on any platform/OS.
It is useful for each platform/OS to require coverage for their own branch.
This can be currently be achieved by using a different configuration file for each platformOS.
It would be helpful that the configuration allows for different ignore patterns for platform/OS, so only one configuration file is needed for all platforms.
One easy way to do this is to iterate the section names in the ini file, extracting any section with pytest in the name, and then finding the most appropriate section for the host platform/OS.
Another approach is to allow the ignore regex to be specified on the command line.
Issue Analytics
- State:
- Created 7 years ago
- Comments:24 (24 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
There’s a new coverage plugin that can do these sorts of conditionals: https://sobolevn.me/2020/02/conditional-coverage
You can already get the effect of the regex being specified on the command line, because environment variables are expanded in the .coveragerc values. So you could use TOXENV in your coverage pragma, or some other environment variable you create just for that purpose.