should Issue Tracker Rss Feed

Created Issue: Add .LessThan(x) and .GreaterThan(x) [9]

annakata — Thu, 14 Feb 2013 13:55:27 GMT

.InRange(a,b) is all very well but it's a bit clunky and not very expressive which is the whole point of using the library is it not?

Commented Issue: Provide signed assemblies. [6]

gsscoder — Sat, 26 Jan 2013 05:43:08 GMT

I would like to mention that you should provide signed assemblies rather than non signed.

Usually the test project is unsigned and why should it be?
This I guess is okay for most of the guys however there is the
not so uncommon problem of testing internal functionality.

And while this is not recommended it is sometimes necessary.
And the way to test internals is to add an InternalVisibileTo attribute in your project.
This requires that the testing project is signed, and thus requires all its referenced assemblies
to be signed.

I will for my project sign it on my own, however given that it
would not hurt you should sign them.

Comments: Hi, I've started using ShouldFluent in the test assembly of this my open source project (http://commandline.codeplex.com/). After users asked my to sign the main assembly, to keep InternalsVisibleTo from main to test project I need to sign test project too. (Now using source inclusion linking files). So I really like to have a singed version of ShouldFluent.dll. Regards, Giacomo Stelluti Scala (gsscoder@gmail.com)

Commented Issue: Adding Messages [7]

erichexter — Tue, 22 May 2012 14:32:47 GMT

It would be good if you could add a customizable error message to each assertion. Sometimes it's a bit difficult to pinpoint exactly which assertion is failing.

Maybe at the end of each assertion there could be a .Message("This assertion failed because x != y").
Comments: That sounds like a good idea

Created Issue: Suggestion to override System.Object.Equals [8]

wusher — Tue, 20 Dec 2011 18:00:01 GMT

I know it is bad practice to override System.Object.Equals to do something other than checking for equality. I think I would be a good idea to alias the method to the Equal method on the Should and the Be objects. I have come across some tests in my project where Should.Be.Equals was used and the tests should have been failing, but weren't. I'm willing to do the coding if you think your project should be altered in such a way.

Also, thanks for the library. My team and I love it.

Created Issue: Adding Messages [7]

jwynveen — Wed, 05 Oct 2011 21:27:59 GMT

Created Issue: Provide signed assemblies. [6]

sovanesyan — Tue, 12 Apr 2011 14:56:39 GMT

Commented Issue: Assembly Generation Failed [5]

akronite — Fri, 26 Nov 2010 03:40:16 GMT

Hi, I seem to be getting this error when referencing Should.Fluent.dll

Error 1 Assembly generation failed -- Referenced assembly 'Should.Fluent' does not have a strong name PGK.Extensions.Tests

Could you please take a look or give me some advise as to why?
Thank you in advance
-Michael T
Comments: Sorry my bad... The issue isn't anything to do with Should Library. My test project have a strongly type key... causing the error message.

Created Issue: Assembly Generation Failed [5]

akronite — Fri, 26 Nov 2010 03:05:23 GMT

Created Issue: Suggestion for adding .ShouldEqual() overload for double which takes a tolerance [4]

behaug — Tue, 19 Oct 2010 12:17:54 GMT

Basically the same as NUnit has with its Assert.AreEqual(double expected, double actual, double tolerance);

Commented Issue: Suggestion for adding .ShouldBeGreaterThan(int, decimal, float, etc.) and .ShouldBeLessThan(int, decimal, float, etc.) [2]

MelGrubb — Thu, 14 Oct 2010 13:25:30 GMT

Also would be nice to have these
Comments: I've taken an important first step toward Mercurial-ness. I have the source pulled down, and I've added the assertions and extensions. I have to write up the tests and the fluent implementations, and then I'll try to contribute it back. I'm not sure how that'll work exactly... maybe emailing the patch to Eric? I'll see what I can manage this weekend.

Commented Issue: Suggestion for adding .ShouldBeGreaterThan(int, decimal, float, etc.) and .ShouldBeLessThan(int, decimal, float, etc.) [2]

MelGrubb — Tue, 12 Oct 2010 16:20:51 GMT

Also would be nice to have these
Comments: I have the code for these, and would like to contribute it to the project. Unfortunately, I still have not found the time to get up to speed on Mercurial... I suck, I know. I can email the classes in if you want them right away, or I can try to carve out an evening and figure the Mercurial thing out. I'm trying, really. The implementation I have is generic, as long as <T> implements IComparable.

Created Issue: Add .ShouldMatch(regex) and .ShouldNotMatch(regex) [3]

pfm102 — Wed, 22 Sep 2010 14:39:47 GMT

Would be rather nice.

Created Issue: Suggestion for adding .ShouldBeGreaterThan(int, decimal, float, etc.) and .ShouldBeLessThan(int, decimal, float, etc.) [2]

joewilson — Fri, 20 Aug 2010 20:13:09 GMT

Also would be nice to have these

Created Issue: Suggestion for adding .ShouldStartWith(string) and .ShouldEndWith(string) [1]

joewilson — Fri, 20 Aug 2010 20:12:17 GMT

Would be nice to have