← Back to team overview

nunit-core team mailing list archive

[Bug 538070] Re: Need a way to generate data when test is executed

 

Hi, hope you don't mind that I jump in on this one,

We're also running into the same problem; our current work-around is to
run all QUnit tests within a single NUnit test. The advantage of running
QUnit tests in a source is to be able to translate 1:1 to NUnit tests so
that our build system reports QUnit test failures individually rather
than in summary, and that our test counts include both NUnit and QUnit
tests. Naturally, running browser-based tests is quite time-consuming in
the normal flow of development, and since we don't want our back-end
developers to be waiting for the full suite of javascript tests when
working in another area of the system, we prefer to defer running of
these until the build on the build server (hence Explicit+Category); UI
devs run the JS tests more regularily, but manually.


Stein Jakob

-- 
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.





Follow ups

References