nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

OK, I understand the use case now and will keep it in mind when this is
implemented.

It's possible that we may be able to avoid the odd use of TestCaseSource and allow you to put your
iterator directly in the test method, which would then report multiple results just as it now dows.

Charlie

-- 
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/538070

Title:
  Need a way to generate data when test is executed

Status in NUnit Test Framework:
  Confirmed

Bug description:
  NUnit 2.5.2 and 2.5.3 run every method targeted by TestCaseSource,
  even if the test targeting it is Explicit or the test fixture is
  Explicit.

  The behaviour I expect is: NUnit shouldn't run a test's TestCaseSource
  if the test itself won't be run.

  Detail:

  I have an expensive TestCaseSource generating a few hundred thousand
  permutations and combinations. I've applied Explicit to both the test
  targeting the source and the fixture surrounding both test and source.

  NUnit console spends ten minutes needlessly constructing test cases
  from the TestCaseSource before ignoring them and proceeding with the
  non-Explicit tests.

  If I throw NotImplementedException from the first line of the
  expensive TestCaseSource. NUnit runs the non-Explicit tests
  immediately. If I put a MessageBox.Show call in the first line, I see
  the message box.