Sharp Tests Ex Alpha2 was released today (download).
In the wiki is now available the Syntax overview.
One of the challenge of this version was rewrite all failure messages to magnify the cause of the failing test.
Similar messages are available for all other assertions.
The next step.Should().Be. the syntax for lambda based assertions as:
const int y = 2;
const int z = 4;
4.Should().Satisfy(x => x == y * y);
2.Should().Satisfy(x => x == z / y);
Why don't you just merge this project with NUnitEx??
I guess you already have the Fluent API and both test frameworks injected inside.
Because, unfotunatelly, each runner has its own tech. to filter the StackTrace and its own Exception (recognized by test-runner).ReplyDelete
I know which are common API but, so far, I can't merge it without think in something like Gallio.
The target of #TestEx is allow MsTest's users to use a test FX without die in the intention.