docs
docs copied to clipboard
nunit
Document how language elements map to NUnit
@CharliePoole commented on Sat Jan 30 2016
This came up in the discussion of nunit/nunit#1187.
We need a page in the wiki that talks about NUnit at a higher level, how classes map to TestFixtures, methods to test cases, etc. The particular point that came up is the idea that constructors of test classes should do very little.
@CharliePoole Tip: You can write nunit/nunit#1229 and GitHub will automatically link it to the referenced issue as well as create a backlink here from that issue. Quite convenient. See: nunit/nunit#1229 😃
Thanks @asbjornu We actually knew that :-) but this issue was automatically moved from the nunit repo by ZenHub, which doesn't translate # references. Can't have everyting I guess.
Ah, I didn't know it was automatically moved by ZenHub. Didn't even know about ZenHub until now. 😄
@asbjornu, unrelated to this issue and we will likely send out an email to the dev list, but if you don't mind, can you also install the ZenHub extension? I've been using it for awhile and have finally convinced @CharliePoole to give it a spin, so would like to start using more of the features.
@asbjornu one warning: you'll see a mix of strange defaults and experiments. We have not yet decided on exactly how to use it.
@rprouse, @CharliePoole, ZenHub looks like an interesting addon to GitHub. Thanks!
@rprouse @CharliePoole I like the idea of this, and would be happy to write it up.
I think this could fall under a new article under "Getting Started" called "Anatomy of an NUnit Test" or similar.
Am I on the right path with what this is looking for? If so, I could write it up with some samples, more like an introductory blog post in a sense.
@SeanKilleen This relates to the NUnit framework, hence not particularly in my wheelhouse these days. :-) However, it does sound like a good idea if you're willing to do it.
You might consider @mentioning the particular team rather than specific individuals when you have questions like this, unless you have a particular reason to limit it to a one person.