MSUnit
Let me be the first to ask for an msunit version 😄 Maybe you could leave this issue as a notification if someone picks it up to do...
@mika76 Thanks for your input! are there certain features that you think are missing that MSUnit can bring to the table?
I would be interested in having an MSUnit version. Currently however this project is designed after XUnit and uses the XUnit naming conventions (Fact/Theory/Skip). A ScenarioTest targeting MSTest would ideally follow a MSUnit style naming convention, e.g.:
[ScenarioTestMethod]
public void MSUnitScenarioTest(ScenarioContext scenario) {
scenario.Test("Foo", () => {
Assert.IsTrue(...);
});
for (var i = 0; i < 5; i++) {
scenario.DataTest("Foo", i, () => {
Assert.IsTrue(i < 5);
});
}
}
Basically there would be a very limited shared surface between the XUnit and MSUnit versions. With that, It would probably be advisable to simply fork this project and keep it as a separate project (Something that I'm not intending on doing through I would not mind helping out if someone wants to take charge in the efforts).