Skip to content

Zero code coverage despite coverage.xml files saying higher #118

@nutjob4life

Description

@nutjob4life

Checked for duplicates

Yes - I've already checked

🐛 Describe the bug

When looking at the various repositories tracked at SonarQube Cloud, the "Coverage" stat for every single project is 0.0%

However, when implementing #104 we saw that coverage was indeed higher and coverage.xml files show coverage as high 97.44% (for peppi. Why this disparity?

🕵️ Expected behavior

I expect coverage numbers of SonarQube Cloud to be reported properly.

📜 To Reproduce

  1. git clone --quiet https://github.com/NASA-PDS/peppi
  2. cd peppi
  3. python3.13 -m venv .venv
  4. rm -f coverage.xml
  5. .venv/bin/pip install --editable '.[dev]'
  6. .venv/bin/tox
  7. xmllint --xpath 'string(/*/@line-rate)' coverage.xml 2>/dev/null

At this point you should see 0.9744.

Now visit https://sonarcloud.io/project/overview?id=NASA-PDS_peppi and note that the coverage is 0.0% throughout

🖥 Environment Info

  • pytest 7.4.4
  • tox 4.11.4
  • SonarSource/sonarqube-scan-action@v6

📚 Version of Software Used

No response

🩺 Test Data / Additional context

No response

🦄 Related requirements

🦄 #xyz

⚙️ Engineering Details

No response

🎉 Integration & Test

No response

Metadata

Metadata

Assignees

Labels

Type

Projects

Status

ToDo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions