I believe your initial statement is incorrect. PNUnit is only intended to run test methods.
I'll have to check this in the code and docs, however, since I haven't looked at it for a while. Assuming I'm right, there still may be a bug, however. PNUnit shouldn't simply fail to report exceptions if a fixture or namespace is specified. Charlie On Mon, Dec 17, 2012 at 1:40 AM, Keld Ølykke <oely...@gmail.com> wrote: > Note! Wrong version - should have been 2.6.2. > > -- > You received this bug notification because you are subscribed to NUnit > Extended Testing Platform. > https://bugs.launchpad.net/bugs/1091138 > > Title: > PNUnit 2.5.2 - Incomplete report when running TestFixture with > multiple TestCases > > To manage notifications about this bug go to: > https://bugs.launchpad.net/nunitv2/+bug/1091138/+subscriptions > -- You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. https://bugs.launchpad.net/bugs/1091138 Title: PNUnit 2.5.2 - Incomplete report when running TestFixture with multiple TestCases Status in NUnit V2 Test Framework: New Bug description: PNUnit will run .conf files where the <TestToRun> may point to a test case, a test fixture or simply a namespace containing test fixtures. However, Asserts and Exceptions are only reported in smoke-errors.log if <TestToRun> points at a test case (method w. Test-attribute). If <TestToRun> points at TestFixture or a namespace the exceptions and asserts are not reported. Kind Regards, Keld Ølykke To manage notifications about this bug go to: https://bugs.launchpad.net/nunitv2/+bug/1091138/+subscriptions _______________________________________________ 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
