Brad Wilson just posted some interesting new attribute usage information on xUnit.net here. And discusses an upcoming feature called [FreezeClock] which will solve an issue I have been having.

He explains [FreezeClock] this way:

Another one we'll do for CodePlex is one I call [FreezeClock], which uses our internal Clock class (a testable replacement for DateTime) which supports the concept of freezing the clock at a moment in time, and then unfreezing when the test is over. This is useful to ensure, for example, that some code under test is calling "Clock.Now", so that you can actually test the value they pushed in some arbitrary amount of time later by simply calling "Clock.Now" again. When we get around to doing that one, I'll make a blog post which shows the Clock class as well as our attribute.

There is another interesting tidbit, another extension called [AssumeIdentity]! Go read for yourself!

Cheers,

Robert Porter