One easy case for understanding: One test tests the generation of test data. It is listed in the middle of the tests. Many tests are using this funtionality and if they doesn't work, they are red. If the fundametal tests run first, it is more clear what error should be searched.
In this case it was not so heavy to find, but it show, what I mean. Of course we can now select by category manually, but automatically sorting is quite better way. -- 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/782117 Title: Categories Priority Status in NUnit Test Framework: New Bug description: Some tests are more important than others. In the Gui, all tests are listed alphabetical. But we have some tests which must be successful. If they are not, about 100 other tests miss. We have lost much time to find out, that not the test does not work, but the tear down which uses one of our function, that does not worked (tested also in an other test for itself). So my purposal is to add a priority to a CategoryAttribut and optionally use the priority of the maximum of all categories. There existes a category-Tab in the gui so simple a checkbox can be added "use categories for test order". I think, this would be very helpfull. Everyone can write ones categories like Important, Basic which high priority or Detailed with low priority. _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : [email protected] Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
