Coverage report run under docker reports incorrect source
See original GitHub issueI am attempting to generate a coverage report for SonarQube. The project is built and tested using a container. The xml file has the source listed <source>/build/project</source>
where as the actual files are under /data/jenkins/workspace/project/lambda
. Is there a way to re-write the source when generating the report? python and libraries are not available outside the container as this is a Jenkins instance.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Coveralls: Error- No source for in my application using Docker ...
The setup I've used successfully is to run unit tests and things like code coverage outside of Docker, and only build and publish...
Read more >HELP : 0% Coverage in sonarqube server - Sonar Community
I'm working on a project where code coverage needs to display in Sonarqube. We are framing dockerfile.test where at ENTRYPOINT nosetests is ...
Read more >Test Coverage Troubleshooting Tips - Code Climate
If you're successfully uploaded reports, but still not seeing coverage info in the UI, it's most likely because you haven't yet sent a...
Read more >Change history for coverage.py - Read the Docs
Feature: Coverage now sets an environment variable, COVERAGE_RUN when running your code with the coverage run command. The value is not important, and...
Read more >How to use the new Code Coverage HTML Report with a ...
I build a docker image with azure devops. Inside the docker build I generate the Unit Test result and coverage report. Since Sprint...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So you’re generating the report outside the running container? That means you’re not using pytest-cov for that. How is that a pytest-cov problem?
closing in favor of https://github.com/nedbat/coveragepy/issues/597