Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options answers only user 8992

Coverage measures the amount of testing done of a certain type. It is always in relation to some kind of measure, for example: statement coverage, branch coverage, etc. (Not restricted to code coverage).

1
vote
covtool.sourceforge.net is quite popular https://opencppcoverage.codeplex.com/ is a good options for windows
answered Mar 29 '16 by Michael Durrant
1
vote
Yes, running tests with or without coverage is the same in terms of testing application functionality and there should be no side affects. The coverage is usually calculated separately from test …
answered Jul 7 '17 by Michael Durrant
1
vote
Yes it is a good practice. I am familiar with coverage reports running for each and every build, both in branches and for master merges. Same as full test suite, so we know immediately and who if coverage deteriorates / tests fail. …
answered Jul 7 '17 by Michael Durrant
0
votes
You question is: do you measure feature coverage, and how do you do it? My answer is: yes, I ask the knowledable users to train me or document them. Consider functions by user type such as regular …
answered Apr 14 '17 by Michael Durrant
6
votes
We're over-testing when we are not adding value It's easy to test to feel good but it's important to do testing that truly adds value as the business defines it. This is a difficult thing to determi …
answered Sep 24 '18 by Michael Durrant