This project is read-only.

NUnitLite Vision

Topics: Developer Forum
May 18, 2006 at 5:36 AM
I've created a page with a simple Vision statement for NUnitLite. We can all edit the page and use this thread to discuss any questions or issues.
Jun 12, 2006 at 7:28 PM
I'm afraid neither the "Why an NUnitLite?" on the home page, nor the vision work for me.

The problem with the example on the home page is that I doubt many developers are aware of the separate Application Domain; I'm sure those we're I'm at now don't know about - or care. I've known about it ever since I've started looking at the code, but never saw an explanation as to why, nor have I sought one. So the example leaves me wondering why not just do that for everyone, instead of making a separate version?

The vision is just a feature (and non-feature) list. What I was expecting from the vision was a less-technical story about the way people might use NUnitLite, and how it might coexist with NUnit. Things like:

- Would the majority of people just starting to add unit testing use one or the other, or is it always a case by case analysis?
- If someone is just trying to learn, or your teaching a course on TDD, which one would be best to use?
- Are there any common situations where you're compelled to use one or the other? Or will a majority or plurality of people do just as well to flip a coin?
- How much overlap is required in the development teams? Or conversely, how soon would they be allowed to diverge incompatibly, if at all?
- What are the criteria for deciding what features to include in both, what in just NUnit, what in just NUnitLite?

I think the last item is the key item, and all the others are questions that build the vision that will answer it.

Aug 29, 2006 at 10:25 PM
I've revised both the Vision and the Features pages. See what you think.