Hi Charlie, I believe we have slight misunderstanding here :( I am talking from the beginning about nunit-console runner and you about GUI runner. I am talking about just having a list of all test cases with all input parameters combinations (like in GUI runner) and you are talking about result states.
Since you are concentrated in your last email on Categories like (NotRunnable, Ignored, Skipped), ...sorry but I do not understand that part for me cathegories are just labels for grouping nunit tests so any name used there is OK to me. sorry I could not contribute more, br, Milan On Fri, Jul 16, 2010 at 11:29 PM, Charlie Poole <char...@nunit.com> wrote: > You misunderstand me. The questions I am asking all pertain to test > cases "before they are run" > I have to decide whether to include each status category I mentioned. > I left out the categories > like success, failure and error, which can only appear after the test is run. > > Please think about what would be most useful for each of these > categories (NotRunnable, > Ignored, Skipped). What happens if your external sequencer is given a > test in each of these > categories? > > Of course, if you are not sure what's best, we can do a simple > implementation that includes > all of these and you can file bugs if it doesn't work well for your case. > > Charlie > > On Fri, Jul 16, 2010 at 1:35 AM, Milan > <milan.vukoslavce...@googlemail.com> wrote: >> Hi Charlie, >> >> I did not go so deep in consideration but I was wanted just "simple" option >> of nunit-console to list all test cases with its input parameters as they >> would be showed in GUI runner. That means before unit tests even run! - just >> to read all test cases from some test assembly, filtered by selected >> cathegory(like in GUI runner). So for example it could be: nunit-console.exe >> milans_test.dll /Category: Testable. >> If the cathegory is set to "Testable", than just unit cases under such >> cathegory should be listed. I usually have 2 cathegories "Testable" and >> "Untestable". >> Listing could be also usefull after test cases have run, but for that case I >> do not have clear "requirements". >> >> Br, >> Milan. >> >> -- >> Feature: Extraction of unit tests from NUnit test asembly and calling >> appropriate one >> https://bugs.launchpad.net/bugs/531873 >> You received this bug notification because you are a member of NUnit >> Developers, which is subscribed to NUnit V2. >> > > -- > Feature: Extraction of unit tests from NUnit test asembly and calling > appropriate one > https://bugs.launchpad.net/bugs/531873 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in NUnit V2 Test Framework: Incomplete > > Bug description: > Hi all, > > in order to integrate NUnit better in the existing solution it would be good > that > by using NUnit(GUI or command line version) over a given Test.exe (where all > necessery test tags/unit tests are allready compiled) to retreive list > of all Unit test names together with its argumens. > > In particular case one have Test.exe which is written in order to test some > library Library.dll and now by using command line one call > NUNit over the Test.exe and to get back list of all Unit tests which are > ready to be tested. Also one could as command line argument submit which > test class or which cathegory is imjortant so that list of the returned tests > is filtered. > > Once the list of all Unit test cases is present (it can be displayed in some > other > industry integrated tool) tester can decide what test case will be executed > by calling > again using command line specific Unit test. It would be also very good that > every test > has its testresult file, having everything in one file makes problem in > accessing only > important test and it is not in accordance with other HW/SW test tool where > every test > has its testresult file. > > Br, > Milan. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/nunitv2/+bug/531873/+subscribe > -- Feature: Extraction of unit tests from NUnit test asembly and calling appropriate one https://bugs.launchpad.net/bugs/531873 You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. Status in NUnit V2 Test Framework: Incomplete Bug description: Hi all, in order to integrate NUnit better in the existing solution it would be good that by using NUnit(GUI or command line version) over a given Test.exe (where all necessery test tags/unit tests are allready compiled) to retreive list of all Unit test names together with its argumens. In particular case one have Test.exe which is written in order to test some library Library.dll and now by using command line one call NUNit over the Test.exe and to get back list of all Unit tests which are ready to be tested. Also one could as command line argument submit which test class or which cathegory is imjortant so that list of the returned tests is filtered. Once the list of all Unit test cases is present (it can be displayed in some other industry integrated tool) tester can decide what test case will be executed by calling again using command line specific Unit test. It would be also very good that every test has its testresult file, having everything in one file makes problem in accessing only important test and it is not in accordance with other HW/SW test tool where every test has its testresult file. Br, Milan. _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : nunit-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
