In SonarQube what is the difference in meaning between the "Lines to Cover" and "Uncovered Lines" metrics?
I am looking at the Coverage report within the Measures tab of a SonarQube analysed C++ project. On that page my summary information is as follows:
What are the differences between the "Lines to Cover" and "Uncovered Lines" metrics?
I have looked on the sonarqube website's Metric Definitions page but the two entries there to do not help me.
Lines to cover - Number of lines of code which could be covered by unit tests (for example, blank lines or full comments lines are not considered as lines to cover).
Uncovered lines - Number of lines of code which are not covered by unit tests.
The way that reads, I would expect that Uncovered Lines would be a higher count than the Lines to cover number, as the former might include blank lines. If sonarqube understood the code somewhat it might also exclude exception handling from the "could be covered by unit tests" number as well.
The given numbers are clearly a reverse of that, so I must not be understanding the meaning correctly.
I have some unit tests run as part of the CI system and their code coverage is compilated using both lcov and gcov. The lcov data is passed through genhtml to make separate coverage report which currently gives data in some cases, so I may have partial misconfiguration issue adding to the confusion.
"Lines to Cover" are the total lines in your "production" code that you should, in a so-called perfect world, have tests for. This is every line in source code files, which is not a comment, blank or similar non-code line.
In the real world, your tests will only cover some of these. The lines that are missed are the "Uncovered Lines".
In other words, you can express "Coverage" as:
"Coverage" = 100% - 100 * "Uncovered Lines" / "Lines to Cover"
- How to pass variables during pytest call via python script(not command line)?
- Unit testcase with parameterized class fixture in Pytest framework is throwing error
- Python Unittest: How to initialize selenium in a class and avoid having the browser opening twice?
- How to check if text is visible with seleniumbase?
- Angular TestBed.inject
- With pytest, for multi-input function looping, how do i assert the answers that i expect based on the responses?
- Inputting a value in a textbox using python seleniumbase
- PyTest: "no tests ran" even though tests were clearly run
- How to run a pytest method multiple times?
- Selenium: I want to choose which browser to use with invocation in Command Prompt
- cross platform unit testing in C
- Implementing xunit in a new programming language
- Create a unit test to verify data from a SQL view in a .NET EF Core project
- Android Unit Tests Requiring Context
- Correct path of mock.patch
- Python unit tests run function after all test
- Random data in Unit Tests?
- Running PostgreSQL in memory only
- How do I test that an offset has been committed or not to Kafka
- How to write an extremely efficient AND testable GUID generator
- No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again
- How to get the call count using Mock @patch?
- How to mock private structs from other mod during testing in rust
- Unit testing in golang
- Mockito ArgumentCaptor needs stubbing even if I use verify?
- Laravel 5 Unit Test - Call to a member function connection() on null
- Unit Testing - How to Compare Two Paged Collections To Assert All Items Different?
- Does PHPUnit have some inbuilt recursive array comparison function?
- Mock instantiated class in class attribute
- Is there a way to test only a subset of unittests in a jupyter notebook?