Brad Wilson and I released xUnit.net V1.0(RC2) today. Brad has a great summary on his blog.
You can download the release from CodePlex. Click here for the release page.
Comments
You can follow this conversation by subscribing to the comment feed for this post.
I don't know if I will move on to xUnit as I am quite satisfied with NUnit.
What I keep on missing however is the inability to have my custom tests tap into the NUnit/xUnit results and statistics such as nr. of tests run/passed/failed.
Also, the Assert* class' static methods all return void when it would have been so easy to return a bool to indicate the result of the assertion so that the user code could use that as well. Would that be improved in xUnit?
I don't know if I will move on to xUnit as I am quite satisfied with NUnit.
What I keep on missing however is the inability to have my custom tests tap into the NUnit/xUnit results and statistics such as nr. of tests run/passed/failed.
Also, the Assert* class' static methods all return void when it would have been so easy to return a bool to indicate the result of the assertion so that the user code could use that as well. Would that be improved in xUnit?
In any case my company is commited to NUnit.
Posted by: Emilio | February 10, 2009 at 05:45 AM
Hello Emilio,
Can you clarify the first comment with regard to custom tests. Are you referring to NUnit or xUnit.net?
Also, with the Assert classes they do not return a value because if the test fails the execution of the test is halted.
Jim
Posted by: James Newkirk | February 14, 2009 at 10:35 AM