Hello.
I have a somewhat advanced question.
Our unit tests are currently written in mstest, however, one has
to go extra mile to simulate combinatorial tests there. So, I am
examining the option of migrating to MbUnit.
In our tests, I simulate combinatorial tests using in-memory data
provider, custom attributes on the methods and populate the data
provider from the ClassInitialize method. All of these are easily done
in MbUnit. There is, however, an additional twist to our setup -
dynamically generated types.
The thing is that a test method input determines the features of
the tested dummy entity and a new dummy entity type may have to be
produced to support these features. The new type is produced by
generating a unique tag type corresponding to the feature spec. This
tag type is then used as the generic type parameter of the
DummyEntity<T> type.
So, each cartesian multiplication product corresponds to some
combination of features to be tested, which correspond to some dummy
entity type, which may have to be dynamically generated, which
instances are tested by the particular test method.
I would like to get an advice on the best way to express these
semantics in MbUnit. I realize, that it may not be supported out of
the box, but I have an impression, that even if MbUnit misses some
functionality, the v3 architecture provides numerous extension points,
which can be utilized to add the missing logic.
Thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MbUnit.User" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/MbUnitUser?hl=en
-~----------~----~----~----~------~----~------~--~---
