The check about controller name should be case insensitive as in MVC
Id #6014 | Release:
| Updated: Oct 30, 2011 at 12:23 PM by fabiomaulo | Created: Oct 26, 2011 at 6:02 PM by fabiomaulo
Make all assertions exceptions serializable, to be able to make cross app-domain assertions.
This is especially useful for integration tests.
Id #6013 | Release:
| Updated: Oct 25, 2011 at 9:03 AM by dux2 | Created: Oct 25, 2011 at 9:03 AM by dux2
Recognize the StartWith method and wiggle the arguments from it; make the test fixture display the same as failure when:
x.Should().StartWith( ... )
Id #6011 | Release:
| Updated: Sep 25, 2011 at 2:38 PM by fabiomaulo | Created: Jun 5, 2011 at 8:43 PM by henke
I'm using the single-source variant from http://satisfyr.codeplex.com/
The above assertion will generate a huge, unmanageable error mess...
Id #6008 | Release:
| Updated: Dec 2, 2010 at 1:23 PM by emn13 | Created: Dec 2, 2010 at 1:23 PM by emn13
Any plans to add this libary to NuPack? Details how to do that - http://nupackpackages.codeplex.com/.
Id #6005 | Release:
| Updated: Sep 25, 2011 at 2:42 PM by fabiomaulo | Created: Oct 21, 2010 at 12:55 PM by chaliy
The syntax with the title (or message in MSTest) in the should looks a bit strange to me. In MSTest I get asserts which looks like this:
viewModel.IsBusy.Should("because it should be set to false ...
Id #5345 | Release:
| Updated: Apr 25, 2011 at 9:28 PM by powerdude | Created: Feb 5, 2010 at 7:25 AM by KoenWillemse
Is a common pattern in fluent interfaces to have a:
Expression<Func<T, TProperty>> to get a propertyinfo in a strongly typed way.
An assert for this type could look like this:
Id #5251 | Release:
| Updated: Jan 24, 2010 at 1:30 PM by jfromaniello | Created: Jan 22, 2010 at 12:25 PM by jfromaniello