+972 52-548-6969
More xUnit tweaks, dynamic test skipping
time to read 1 min | 99 words
For a long time, xUnit’s dev has resisted adding support for skipping a test dynamically. You could create your own Fact class and handle that yourself, but that was quite a lot of work, for something very specific.
In RavenDB, we had the need to dynamically decide whatever the test can run based on the actual test situation, so I decided to add this to our xUnit fork. This turned out to be really simple to do. Just three lines of code 
Comments
I really like xUnit, but some of their dogmatic choices really irritate me. This is one of those times they choose to be dogmatic over actually getting shit done.
They make users jump through hoops just so they can stay on their high and mighty horse.
I wonder how many contributors to xUnit have all built the very same things they refuse to allow into the project in their own real systems. I suspect it would be more than half.
I went the attribute based approach inheriting from [Fact].
This way I had a global setting to run/ignore tests marked with the [OptionallyIgnoreTestFact] attribute at run-time.
https://github.com/chrismckelt/XUnit.OptionallyIgnore
@ChrisMarisic, +1 against xUnit dogmatism. For example, Assert with a message http://xunit.codeplex.com/workitem/4638 That's why I prefer to stick to NUnit. It's simple and let's you express in your own way.
@Scooletz it's crazy to me to see the xUnit official response was basically "you suck". Providing additional context is ALWAYS A win. Boggles my mind to see people opposed to additional context. Everything is meaningless without context.
edit if slorion isn't your codeplex account, replace "you" with "slorion"
Comment preview