Replies: 1 comment
-
If anyone else has this question, I ended up skipping the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
I am trying to work out an approach for parameterizing my test cases.
My test source is organized in a hierarchy, where the top level of the hierarchy maps to a TestFixture and each of the child elements in the hierarchy maps to a TestCase. I have reviewed #2707 and #2950 and think I understand why that is not possible, but I am not sure what I can do instead.
The current organization of the test data is a flat list, with an identifier that includes the hierarchy, for example:
In #2707 (comment) the order is listed as:
So I could create a
TestFixtureSource
to create test fixtures forapple
andorange
and aTestCaseSource
to (independently?) create test cases forapple.honeycrisp
,apple.red_delicious
,apple.mcintosh
,orange.mandarin
,orange.tangerine
,orange.navel
.What I'm not clear about is the access to data each test will have as it is run. One thought is I could make a static dictionary of test fixtures as they are created, and then as each test case was executed, it would look up the test fixture based on its identifier. So
apple.honeycrisp
would run, look up and use theapple
test fixture, thenorange.mandarin
would run, look up theorange
test fixture, and so on.Is that a reasonable approach?
Beta Was this translation helpful? Give feedback.
All reactions