You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- 1Thank you for your response. I was using xunit.console.exe. I am aware that it is not a good solution, and it wasn't really the intended use. The reason I needed it was to debug some string operations while creating a new class using TDD.kfuglsang– kfuglsang2011-08-23 12:04:53 +00:00Commented Aug 23, 2011 at 12:04
- 49"In general, it's a bad road to go down to be reliant on logging and tests." - true, but using Console.Writeline to output stuff WHILE I'm setting up the tests is hugely helpful. Sometimes I'm testing a method and need to see the output of the method (for example if something serialized correctly when doing custom serialization) to insert back into the test to compare against.Anshul– Anshul2014-12-07 16:43:59 +00:00Commented Dec 7, 2014 at 16:43
- 19Switched to NUnit, which captures stdout. If a test fails, it's greatly important to know what's going on in the production code, in which case the logging becomes important. Injecting any test framework specific dependency into the production code just so I can see the output while running tests is just ridiculous. And I found that when people start telling you "xxx is a bad idea...", although sounds cool, it usually is an excuse to the incompetency of the tool you're having issue with.KFL– KFL2016-06-12 15:51:37 +00:00Commented Jun 12, 2016 at 15:51
- 36So the xUnit authors think that having tests that fail with no information on WHY is a great design?Warren P– Warren P2016-10-21 16:00:56 +00:00Commented Oct 21, 2016 at 16:00
- 32I disagree strongly on your comment regarding "it's a bad road to go down to be reliant on logging and tests". We run integration tests (apart from unit tests), that if broken, it is extremely helpful to see the logging information to understand what exactly failed before further investigation.z0mbi3– z0mbi32017-09-01 12:47:08 +00:00Commented Sep 1, 2017 at 12:47
| Show 7 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. python-3.x), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you