Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 6,026 | Comments: 44,842

filter by tags archive

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 Smile



Chris Marisic

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.

chris mckelt

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.


@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.

Chris Marisic

@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.

Chris Marisic

edit if slorion isn't your codeplex account, replace "you" with "slorion"

Comment preview

Comments have been closed on this topic.


No future posts left, oh my!


  1. Technical observations from my wife (3):
    13 Nov 2015 - Production issues
  2. Production postmortem (13):
    13 Nov 2015 - The case of the “it is slow on that machine (only)”
  3. Speaking (5):
    09 Nov 2015 - Community talk in Kiev, Ukraine–What does it take to be a good developer
  4. Find the bug (5):
    11 Sep 2015 - The concurrent memory buster
  5. Buffer allocation strategies (3):
    09 Sep 2015 - Bad usage patterns
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats