nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

We'll reconsider this in 3.0

** Changed in: nunitv2
       Status: Incomplete => Confirmed

** Project changed: nunitv2 => nunit-3.0

-- 
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 Test Framework: Confirmed

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.