TestCaseSource cannot refer to a parameterized test fixture #33
Labels
Milestone
Comments
|
Just got bit by this one. My work around was inheritance and setting the variable value I wanted in the child constructors. I'm looking forward to the fix. |
markwhitfeld
pushed a commit
to markwhitfeld/nunit-framework
that referenced
this issue
Nov 11, 2013
"TestCaseSource cannot refer to a parameterized test fixture"
- allow specifying constructor parameters after data source method name
- for the case where no method name would be required for the data
source (ie, when the data source class itself implements
IEnumerable), require the user to provide null for the method name
- proposed to cater for the case where the only parameter to the
constructor is a string
markwhitfeld
pushed a commit
to markwhitfeld/nunit-framework
that referenced
this issue
Nov 11, 2013
after getting this test to fail whilst working on Issue nunit#33 - original code tried to get true/false variance in 10 attempts: the new test attempts up to 10000 times to get variance, quitting after the first time variance is found and bailing out with a useful message if variance isn't found in 10000 attempts.
|
Since this is done, I'm moving it to the alpha1 milestone |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TestCaseSource always instantiates the object providing data using the default constructor. Parameterized fixtures usually don't have one and adding one would mean that no parameters were available to generate data.
From https://bugs.launchpad.net/nunit-3.0/+bug/1239046
The text was updated successfully, but these errors were encountered: