GreenMoose
My feedback
42 results found
-
8 votesGreenMoose supported this idea ·
-
1 voteGreenMoose shared this idea ·
-
1 voteGreenMoose shared this idea ·
-
1 voteGreenMoose shared this idea ·
-
24 votesGreenMoose supported this idea ·
-
1 voteGreenMoose shared this idea ·
-
1 vote
An error occurred while saving the comment GreenMoose shared this idea · -
1 voteGreenMoose shared this idea ·
-
1 voteGreenMoose shared this idea ·
-
5 votesGreenMoose supported this idea ·
-
8 votes
An error occurred while saving the comment GreenMoose commentedI would like to chip in that this is also useful for normal log output. For instance I have diferent indent for app and test log output (and most often it is the test output I am interested in), the default word wrapping makes the log output windoe unnecessary cluttered to find my test log lines. See example at https://i.imgur.com/KbjSkr1.png
GreenMoose supported this idea · -
29 votesGreenMoose supported this idea ·
-
2 votes
An error occurred while saving the comment GreenMoose commented+1 for full coverage attribute. I often add new code (test fixtures/prod code) which I know is "NCrunch covered" now, but want NCrunch console running on CI server fail if those classes drops in coverage (but allow other code to be non covered). This would be a killer feature for CI setups with NCrunch.
GreenMoose supported this idea · -
1 voteGreenMoose shared this idea ·
-
2 votesGreenMoose shared this idea ·
-
1 voteGreenMoose shared this idea ·
-
1 voteGreenMoose shared this idea ·
-
2 votesGreenMoose shared this idea ·
-
2 votesGreenMoose shared this idea ·
-
2 votesGreenMoose supported this idea ·
...Or a "light" version would be e.g. to append it in Status e.g. "Build successful with warnings" vs "Build successful", alternatively a separate column with warning count.
(I have "treat compile errors as warnings" enabled in Release bulids but not in Debug since they might temporary exist during work in progress, and CI server builds in Release)