#TestsEx 0.3.0 was released yesterday.
var var2 = 2;
2.Satisfy(a => var2 == a);
1.Satisfy(a => a == 1 || a != 0);
The mayor advantage of the “Satisfy syntax” is that it is pure C#; perhaps is less readable but you don’t need to know the name of an assertion and its “extensible limit” is the same you have in C#. Even if this feature is available and can be used right now, we are working to improve the failure message.
The breaking change
Perhaps this is the first time I’m happy to announce a breaking change. Starting from this release, to use #TestsEx extensions, you must specify the using clause.
Why ? #TestsEx, now can be used with your preferred unit test framework.
You must add the reference to SharpTestsEx.MSTest.dll in your test project.
You must add the reference to SharpTestsEx.NUnit.dll in your test project.
You must add the reference to SharpTestsEx.xUnit.dll in your test project.
For others frameworks you can use SharpTestsEx.dll but, probably, you will see SharpTestsEx in the stack trace of the failure message in your test runner.
If you are working in various projects, using various unit tests frameworks, now you have one more reason to use #TestsEx.
Sharp Tests Extensions is a compendium of commons “extensible extensions” to work with your preferred unit test framework and not another test framework.