Source code checked in, #68323
Finished another method of the IComparable<T> assertions
View ArticleCommented Issue: current IComparable asserts aren't available for IComparable...
same as the title, don't really think I can add much more,btw, started using your library today, and so far loving it, great work.Comments: Associated with changeset 68323.
View ArticleCommented Issue: current IComparable asserts aren't available for IComparable...
same as the title, don't really think I can add much more,btw, started using your library today, and so far loving it, great work.Comments: Associated with changeset 68357.
View ArticleCommented Issue: current IComparable asserts aren't available for IComparable...
same as the title, don't really think I can add much more,btw, started using your library today, and so far loving it, great work.Comments: Associated with changeset 68358.
View ArticleReleased: Release 1.5.0 (Jun 29, 2011)
Whats New Extensions for representing date and/or time values in fluent API Added string.Should().NotContain(), ContainEquivalentOf() and NotContainEquivalentOf() Added string.Should().BeBlank() and...
View ArticleUpdated Release: Release 1.5.0 (Jun 29, 2011)
Whats New Extensions for representing date and/or time values in fluent API Added string.Should().NotContain(), ContainEquivalentOf() and NotContainEquivalentOf() Added string.Should().BeBlank() and...
View ArticleReleased: Release 1.5.0 (Jun 29, 2011)
Whats New Extensions for representing date and/or time values in fluent API Added string.Should().NotContain(), ContainEquivalentOf() and NotContainEquivalentOf() Added string.Should().BeBlank() and...
View ArticleUpdated Release: Release 1.5.0 (Jun 29, 2011)
Whats New Extensions for representing date and/or time values in fluent API Added string.Should().NotContain(), ContainEquivalentOf() and NotContainEquivalentOf() Added string.Should().BeBlank() and...
View ArticleClosed Issue: Add BeNullOrWhiteSpace() & NotBeNullOrWhiteSpace() [11016]
Duplicate the current BeNullOrEmpty() & NotBeNullOrEmpty() but test for NullOrWhiteSpace.Example.string actual = "ABCDEFGHI";actual.Should().NotBeNullOrWhiteSpace() // does not throw...
View ArticleClosed Issue: Test framework detection not working [11012]
Instead of trying to detect the framework using Assembly.Load Method, we should use something like thisAppDomain.CurrentDomain.GetAssemblies().Any(a => a.GetName().Name =...
View ArticleClosed Issue: Better readability with extension methods on int [10087]
Include Minutes(), Hours() and Days() extension methods on integers, for better readability of DateTime assertions.For example:public static TimeSpan Minutes(this int source){ return...
View ArticleClosed Issue: When a different exception is detected, it should include the...
Currently, when another exception is thrown than the one expected, it is difficult to determine what went wrong, because the Message and Stacktrace is not shown.Comments:
View ArticleClosed Issue: Property comparison should be a bit smarter [10683]
The ShouldHave().AllProperties() and corresponding variants should not just use the Equals() method to compare individual properties, but attempt to use the built-in .Be()/.Equal() extension methodes...
View ArticleClosed Issue: Please update documentation how to use extension methods to add...
In the documentation, there is Verification.Fail("Expected whatever..."); used to fail the test. I assume that is is now done with Execute.Verification or Execute.Fail.Could you please update the...
View ArticleClosed Issue: Should().NotBeEmpty() enumerates whole collection [10362]
I have a service that returns IEnumerable<T> one by one very slowly (or even returns stream that never ends).I want to test that it actually returns something so I do...
View Article