option to not running code coverage if a test fails

Is this including the option to not running code coverage if a test fails or is that another issue?

3 comments
Comment actions Permalink

Hi

Not sure I understand the request. Coverage is started before test execution, and they are performed in parallel.
Could you explain what problems do you experience?

Thanks

0
Comment actions Permalink

Ah off course. I actually meant the time spent for generating cover report, which for us (so far at least) is waste of time if tests fail.

Example:
<...>
[11:02:12]: Processing 1 coverage report(s)
<...>
[11:02:25]: Generate dotCover HTML report
<...>[11:06:44]: DotCover statement coverage was: 3864 of 7396 ( 52.244453%)
<...>
[11:06:44]: Publishing artifacts
<...>
[11:08:25]: Build finished


(52% coverage is low due to failing unit tests so it isn't of any importance to us)
Here there is roughly 6 minutes "dead time" for which we have to wait until build server starts another build on the agent.

Thus the actual request I guess is an option to skip the docCover html report if a unit test fail.

0
Comment actions Permalink

(created feature request http://youtrack.jetbrains.net/issue/TW-16048 since as I understood this is not part of the publishing artifacts issue)

0

Please sign in to leave a comment.