Yes, that is right. The person who is responsible for the test shall see that there must be something done in future but not as error. The tests shall not run. The person who implements the feature shall be able to run the test without any code changes in the test itself.
Perhaps an own color would clearyfy. By the way, it should be possible to run all explicit tests of a class or a assembly with one click. Perhaps an own entry in the context menu. -- 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: New 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! _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : [email protected] Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
