Forum member

CharliePoole

2 posts

Posts by CharliePoole

  1. Inconclusive result in NUnit TestCaseSource

    Yes, TestCaseSource was the first feature that basically made it impractical for any runner to just "figure out" the tests by looking at the assembly. You really have to execute the code. Other features like that are Pairwise combinations of parameter values (because it's non-deterministic) and to s…

    28 Jan 2015 05:30 UTC

  2. Inconclusive result in NUnit TestCaseSource

    I noticed this while browsing here for another reason and thought I'd mention the following for whomever it may help - i.e. users or the developer of the runner. In NUnit we do _not_ provide a unique test name. In fact, we designed it so that test names don't have to be unique. This causes proble…

    28 Jan 2015 01:55 UTC