Mixing
Excluding code from coverage stats in Xcode 7
I have enabled code coverage statistics in Xcode 7.0 and Objective C (like this) and it's working well.
Is it possible to mark some source lines so that they are ignored by the coverage report? If I was using lcov then I could use LCOV_EXCL_START and LCOV_EXCL_END markers (as in How to tell lcov to ignore lines in the source files) but Xcode doesn't recognize those.
Does Xcode have an alternative mechanism for doing this?
xcode unit-testing xcode7
edited Dec 21 '17 at 13:08
Krishnan
6,3441980149
asked Sep 22 '15 at 1:26
Ewan MellorEwan Mellor
5,4451636
add a comment |
I have enabled code coverage statistics in Xcode 7.0 and Objective C (like this) and it's working well.
Is it possible to mark some source lines so that they are ignored by the coverage report? If I was using lcov then I could use LCOV_EXCL_START and LCOV_EXCL_END markers (as in How to tell lcov to ignore lines in the source files) but Xcode doesn't recognize those.
Does Xcode have an alternative mechanism for doing this?
xcode unit-testing xcode7
edited Dec 21 '17 at 13:08
Krishnan
6,3441980149
asked Sep 22 '15 at 1:26
Ewan MellorEwan Mellor
5,4451636
1
When I was young and unexperienced I was doing that too, then I realized that it's futile attempting to reach 100% coverage by ignoring some parts of code. Don't try to play your reports by ignoring code.
– Sulthan
Sep 30 '15 at 0:47
The only way I can see is using a post-action for Test when you find theCoverage.profdatafile in the build directory and update it. It's probably possible to export it to gcov using llvm-cov tool.
– Sulthan
Sep 30 '15 at 1:58
7
@Sulthan I am neither young nor inexperienced. I would like to exclude lines such as asserts that a particular line is unreachable. There's a lot of value in knowing at a glance that every reachable line in a function is covered, and not having to check whether the bright red line in Xcode is actually just an assert.
– Ewan Mellor
Sep 30 '15 at 4:37
@Sulthan I'm not interested in exporting to another tool; I could do that before. The point of this question is to use the display in Xcode 7.
– Ewan Mellor
Sep 30 '15 at 4:38
That's what I meant, However there is no such functionality by default so if you want to do that, you have to update the coverage file - which is a binary file. So, one way of doing that would be to convert the new profdata format togcovformat (which is human readable and to ignore lines you can just use a smartsedcommand) and then convert it back toprofdata. and let Xcode read the updated file. The only technical problem is the profdata - gcov conversion.
– Sulthan
Sep 30 '15 at 11:33
add a comment |
I have enabled code coverage statistics in Xcode 7.0 and Objective C (like this) and it's working well.
Is it possible to mark some source lines so that they are ignored by the coverage report? If I was using lcov then I could use LCOV_EXCL_START and LCOV_EXCL_END markers (as in How to tell lcov to ignore lines in the source files) but Xcode doesn't recognize those.
Does Xcode have an alternative mechanism for doing this?
xcode unit-testing xcode7
edited Dec 21 '17 at 13:08
Krishnan
6,3441980149
asked Sep 22 '15 at 1:26
Ewan MellorEwan Mellor
5,4451636
I have enabled code coverage statistics in Xcode 7.0 and Objective C (like this) and it's working well.
Is it possible to mark some source lines so that they are ignored by the coverage report? If I was using lcov then I could use LCOV_EXCL_START and LCOV_EXCL_END markers (as in How to tell lcov to ignore lines in the source files) but Xcode doesn't recognize those.
Does Xcode have an alternative mechanism for doing this?
xcode unit-testing xcode7
xcode unit-testing xcode7
edited Dec 21 '17 at 13:08
Krishnan
6,3441980149
asked Sep 22 '15 at 1:26
Ewan MellorEwan Mellor
5,4451636
edited Dec 21 '17 at 13:08
Krishnan
6,3441980149
asked Sep 22 '15 at 1:26
Ewan MellorEwan Mellor
5,4451636
edited Dec 21 '17 at 13:08
Krishnan
6,3441980149
edited Dec 21 '17 at 13:08
Krishnan
6,3441980149
edited Dec 21 '17 at 13:08
Krishnan
6,3441980149
6,3441980149
asked Sep 22 '15 at 1:26
Ewan MellorEwan Mellor
5,4451636
asked Sep 22 '15 at 1:26
Ewan MellorEwan Mellor
5,4451636
asked Sep 22 '15 at 1:26
Ewan MellorEwan Mellor
5,4451636
5,4451636
1
When I was young and unexperienced I was doing that too, then I realized that it's futile attempting to reach 100% coverage by ignoring some parts of code. Don't try to play your reports by ignoring code.
– Sulthan
Sep 30 '15 at 0:47
The only way I can see is using a post-action for Test when you find theCoverage.profdatafile in the build directory and update it. It's probably possible to export it to gcov using llvm-cov tool.
– Sulthan
Sep 30 '15 at 1:58
7
@Sulthan I am neither young nor inexperienced. I would like to exclude lines such as asserts that a particular line is unreachable. There's a lot of value in knowing at a glance that every reachable line in a function is covered, and not having to check whether the bright red line in Xcode is actually just an assert.
– Ewan Mellor
Sep 30 '15 at 4:37
@Sulthan I'm not interested in exporting to another tool; I could do that before. The point of this question is to use the display in Xcode 7.
– Ewan Mellor
Sep 30 '15 at 4:38
That's what I meant, However there is no such functionality by default so if you want to do that, you have to update the coverage file - which is a binary file. So, one way of doing that would be to convert the new profdata format togcovformat (which is human readable and to ignore lines you can just use a smartsedcommand) and then convert it back toprofdata. and let Xcode read the updated file. The only technical problem is the profdata - gcov conversion.
– Sulthan
Sep 30 '15 at 11:33
add a comment |
1
When I was young and unexperienced I was doing that too, then I realized that it's futile attempting to reach 100% coverage by ignoring some parts of code. Don't try to play your reports by ignoring code.
– Sulthan
Sep 30 '15 at 0:47
The only way I can see is using a post-action for Test when you find theCoverage.profdatafile in the build directory and update it. It's probably possible to export it to gcov using llvm-cov tool.
– Sulthan
Sep 30 '15 at 1:58
7
@Sulthan I am neither young nor inexperienced. I would like to exclude lines such as asserts that a particular line is unreachable. There's a lot of value in knowing at a glance that every reachable line in a function is covered, and not having to check whether the bright red line in Xcode is actually just an assert.
– Ewan Mellor
Sep 30 '15 at 4:37
@Sulthan I'm not interested in exporting to another tool; I could do that before. The point of this question is to use the display in Xcode 7.
– Ewan Mellor
Sep 30 '15 at 4:38
That's what I meant, However there is no such functionality by default so if you want to do that, you have to update the coverage file - which is a binary file. So, one way of doing that would be to convert the new profdata format togcovformat (which is human readable and to ignore lines you can just use a smartsedcommand) and then convert it back toprofdata. and let Xcode read the updated file. The only technical problem is the profdata - gcov conversion.
– Sulthan
Sep 30 '15 at 11:33
1
1
When I was young and unexperienced I was doing that too, then I realized that it's futile attempting to reach 100% coverage by ignoring some parts of code. Don't try to play your reports by ignoring code.
– Sulthan
Sep 30 '15 at 0:47
When I was young and unexperienced I was doing that too, then I realized that it's futile attempting to reach 100% coverage by ignoring some parts of code. Don't try to play your reports by ignoring code.
– Sulthan
Sep 30 '15 at 0:47
The only way I can see is using a post-action for Test when you find the
Coverage.profdata file in the build directory and update it. It's probably possible to export it to gcov using llvm-cov tool.– Sulthan
Sep 30 '15 at 1:58
The only way I can see is using a post-action for Test when you find the
Coverage.profdata file in the build directory and update it. It's probably possible to export it to gcov using llvm-cov tool.– Sulthan
Sep 30 '15 at 1:58
7
7
@Sulthan I am neither young nor inexperienced. I would like to exclude lines such as asserts that a particular line is unreachable. There's a lot of value in knowing at a glance that every reachable line in a function is covered, and not having to check whether the bright red line in Xcode is actually just an assert.
– Ewan Mellor
Sep 30 '15 at 4:37
@Sulthan I am neither young nor inexperienced. I would like to exclude lines such as asserts that a particular line is unreachable. There's a lot of value in knowing at a glance that every reachable line in a function is covered, and not having to check whether the bright red line in Xcode is actually just an assert.
– Ewan Mellor
Sep 30 '15 at 4:37
@Sulthan I'm not interested in exporting to another tool; I could do that before. The point of this question is to use the display in Xcode 7.
– Ewan Mellor
Sep 30 '15 at 4:38
@Sulthan I'm not interested in exporting to another tool; I could do that before. The point of this question is to use the display in Xcode 7.
– Ewan Mellor
Sep 30 '15 at 4:38
That's what I meant, However there is no such functionality by default so if you want to do that, you have to update the coverage file - which is a binary file. So, one way of doing that would be to convert the new profdata format to
gcov format (which is human readable and to ignore lines you can just use a smart sed command) and then convert it back to profdata. and let Xcode read the updated file. The only technical problem is the profdata - gcov conversion.– Sulthan
Sep 30 '15 at 11:33
That's what I meant, However there is no such functionality by default so if you want to do that, you have to update the coverage file - which is a binary file. So, one way of doing that would be to convert the new profdata format to
gcov format (which is human readable and to ignore lines you can just use a smart sed command) and then convert it back to profdata. and let Xcode read the updated file. The only technical problem is the profdata - gcov conversion.– Sulthan
Sep 30 '15 at 11:33
add a comment |
1 Answer
1
active
oldest
votes
Xcode7 and later (based on some forum posts), the coverage system uses LLVM's coverage generation and reporting mechanisms, the format for which is detailed at http://llvm.org/docs/CoverageMappingFormat.html. As of Xcode 9, this format does not support any means of exclusion of lines (or other structures).
The resulting mapping is exported into a consumable format (txt or html) by llvm-cov, which also doesn't really have much in the way of exclusion mechanisms. llvm-cov does have some simple thresholding for only reporting on "greater than" or "less than" coverage for both lines and regions, but I suspect that's not entirely what you're after based on the question above.
answered Aug 28 '17 at 20:29
heckjheckj
4,63622737
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f32706968%2fexcluding-code-from-coverage-stats-in-xcode-7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Xcode7 and later (based on some forum posts), the coverage system uses LLVM's coverage generation and reporting mechanisms, the format for which is detailed at http://llvm.org/docs/CoverageMappingFormat.html. As of Xcode 9, this format does not support any means of exclusion of lines (or other structures).
The resulting mapping is exported into a consumable format (txt or html) by llvm-cov, which also doesn't really have much in the way of exclusion mechanisms. llvm-cov does have some simple thresholding for only reporting on "greater than" or "less than" coverage for both lines and regions, but I suspect that's not entirely what you're after based on the question above.
answered Aug 28 '17 at 20:29
heckjheckj
4,63622737
add a comment |
Xcode7 and later (based on some forum posts), the coverage system uses LLVM's coverage generation and reporting mechanisms, the format for which is detailed at http://llvm.org/docs/CoverageMappingFormat.html. As of Xcode 9, this format does not support any means of exclusion of lines (or other structures).
The resulting mapping is exported into a consumable format (txt or html) by llvm-cov, which also doesn't really have much in the way of exclusion mechanisms. llvm-cov does have some simple thresholding for only reporting on "greater than" or "less than" coverage for both lines and regions, but I suspect that's not entirely what you're after based on the question above.
answered Aug 28 '17 at 20:29
heckjheckj
4,63622737
add a comment |
Xcode7 and later (based on some forum posts), the coverage system uses LLVM's coverage generation and reporting mechanisms, the format for which is detailed at http://llvm.org/docs/CoverageMappingFormat.html. As of Xcode 9, this format does not support any means of exclusion of lines (or other structures).
The resulting mapping is exported into a consumable format (txt or html) by llvm-cov, which also doesn't really have much in the way of exclusion mechanisms. llvm-cov does have some simple thresholding for only reporting on "greater than" or "less than" coverage for both lines and regions, but I suspect that's not entirely what you're after based on the question above.
answered Aug 28 '17 at 20:29
heckjheckj
4,63622737
Xcode7 and later (based on some forum posts), the coverage system uses LLVM's coverage generation and reporting mechanisms, the format for which is detailed at http://llvm.org/docs/CoverageMappingFormat.html. As of Xcode 9, this format does not support any means of exclusion of lines (or other structures).
The resulting mapping is exported into a consumable format (txt or html) by llvm-cov, which also doesn't really have much in the way of exclusion mechanisms. llvm-cov does have some simple thresholding for only reporting on "greater than" or "less than" coverage for both lines and regions, but I suspect that's not entirely what you're after based on the question above.
answered Aug 28 '17 at 20:29
heckjheckj
4,63622737
answered Aug 28 '17 at 20:29
heckjheckj
4,63622737
answered Aug 28 '17 at 20:29
heckjheckj
4,63622737
answered Aug 28 '17 at 20:29
heckjheckj
4,63622737
4,63622737
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f32706968%2fexcluding-code-from-coverage-stats-in-xcode-7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
When I was young and unexperienced I was doing that too, then I realized that it's futile attempting to reach 100% coverage by ignoring some parts of code. Don't try to play your reports by ignoring code.
– Sulthan
Sep 30 '15 at 0:47
The only way I can see is using a post-action for Test when you find the
Coverage.profdatafile in the build directory and update it. It's probably possible to export it to gcov using llvm-cov tool.– Sulthan
Sep 30 '15 at 1:58
7
@Sulthan I am neither young nor inexperienced. I would like to exclude lines such as asserts that a particular line is unreachable. There's a lot of value in knowing at a glance that every reachable line in a function is covered, and not having to check whether the bright red line in Xcode is actually just an assert.
– Ewan Mellor
Sep 30 '15 at 4:37
@Sulthan I'm not interested in exporting to another tool; I could do that before. The point of this question is to use the display in Xcode 7.
– Ewan Mellor
Sep 30 '15 at 4:38
That's what I meant, However there is no such functionality by default so if you want to do that, you have to update the coverage file - which is a binary file. So, one way of doing that would be to convert the new profdata format to
gcovformat (which is human readable and to ignore lines you can just use a smartsedcommand) and then convert it back toprofdata. and let Xcode read the updated file. The only technical problem is the profdata - gcov conversion.– Sulthan
Sep 30 '15 at 11:33