nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

1. Bugs are scheduled in milestones according to the purpose of the
milestone. The 2.9.6 milestone will primarily consist of fixes that
bring NUnit 3.0 up to the same level as NUnit 2.6.

2. This change is major because it potentially introduces another result
type into NUnit. We will need to discuss it on the list and decide
whether this is an instance of an existing ResultState/TestStatus or
requires a new one. We will need to discuss whether it should be built-
in to NUnit or if there should instead be a general way to create such
extensions. I'll start all that discussion when some other things are
complete that have a higher priority - or you could start it yourself if
you like.

3. To be clear, you didn't deliver code to implement this feature but
only code showing how it could be used in a test. That's OK, of course,
and we'll figure out how to implement it after we decide about #2.

Charlie

-- 
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/777810

Title:
  explicit and ignore

Status in NUnit Test Framework:
  Triaged

Bug description:
  First the problem:
  We make a test, that could not be satisfied up to now, because the implementation of the functionality is not ready. We give him the attribute explicit, so the developer can run the test while he implements the functionality. But for the person who looks at the tests, he didn't see the test. So we make a empty copy of the test and give hin the attribute ignore.
  If we give the test both attributes, explicit and ignore, the test is not runable under the gui.

  A possibility would be that ignored tests can be run if a special option is set (perhaps on the tab for categories or command line).
  This would be a very nice feature!

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-3.0/+bug/777810/+subscriptions