Should Assertion Library

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)

Updated Wiki: Home

erichexter — Sun, 13 Jan 2013 13:16:44 GMT

This project is now hosted at : https://github.com/erichexter/Should

Updated Wiki: Home

erichexter — Sun, 13 Jan 2013 13:16:08 GMT

This project is now hosted at : https://github.com/erichexter/Should

Reviewed: 1.1.12 (dic 14, 2012)

gsscoder — Fri, 14 Dec 2012 12:43:36 GMT

Rated 5 Stars (out of 5) - Excellent work! Thank you...

New Post: New Release and Nuget package?

erichexter — Wed, 23 May 2012 18:27:59 GMT

I filled out their form and they are going to hook up the CI off of the current nant build.. once we get it working we can conver that old build to something newer.

The source is now on github.com/erichexter/should feel free to submit pull requests.

Updated Wiki: Home

erichexter — Tue, 22 May 2012 17:57:47 GMT

Project Description

The Should Assertion Library provides a set of extension methods for test assertions for AAA and BDD style tests. It provides assertions only, and as a result it is Test runner agnostic. The assertions are a direct fork of the xUnit test assertions. This project was born because test runners Should be independent of the the assertions!

Install should from nuget

PM> install-package should

The following example shows some of the the assertions that are available for objects, booleans, string, and collections.

public void Should_assertions()
{
    object obj = null;
    obj.ShouldBeNull();

    obj = new object();
    obj.ShouldBeType(typeof(object));
    obj.ShouldEqual(obj);
    obj.ShouldNotBeNull();
    obj.ShouldNotBeSameAs(new object());
    obj.ShouldNotBeType(typeof(string));
    obj.ShouldNotEqual("foo");

    obj = "x";
    obj.ShouldNotBeInRange("y", "z");
    obj.ShouldBeInRange("a", "z");
    obj.ShouldBeSameAs("x");

    "This String".ShouldContain("This");
    "This String".ShouldNotBeEmpty();
    "This String".ShouldNotContain("foobar");

    false.ShouldBeFalse();
    true.ShouldBeTrue();

    var list = new List<object>();
    list.ShouldBeEmpty();
    list.ShouldNotContain(new object());

    var item = new object();
    list.Add(item);
    list.ShouldNotBeEmpty();
    list.ShouldContain(item);
}

Should also provides a fluent API. Here are the same assertions as above using the fluent API. Should.Fluent is a direct port of ShouldIt.

Install should from nuget

PhM> install-package ShouldFluent

public void Should_fluent_assertions()
{
    object obj = null;
    obj.Should().Be.Null();

    obj = new object();
    obj.Should().Be.OfType(typeof(object));
    obj.Should().Equal(obj);
    obj.Should().Not.Be.Null();
    obj.Should().Not.Be.SameAs(new object());
    obj.Should().Not.Be.OfType<string>();
    obj.Should().Not.Equal("foo");

    obj = "x";
    obj.Should().Not.Be.InRange("y", "z");
    obj.Should().Be.InRange("a", "z");
    obj.Should().Be.SameAs("x");

    "This String".Should().Contain("This");
    "This String".Should().Not.Be.Empty();
    "This String".Should().Not.Contain("foobar");

    false.Should().Be.False();
    true.Should().Be.True();

    var list = new List<object>();
    list.Should().Count.Zero();
    list.Should().Not.Contain.Item(new object());

    var item = new object();
    list.Add(item);
    list.Should().Not.Be.Empty();
    list.Should().Contain.Item(item);
};

Here are some additional examples of assertions using the fluent API:

public void Should_fluent_assertions()
{
    var numbers = new List<int> { 1, 1, 2, 3 };
    numbers.Should().Contain.Any(x => x == 1);
    numbers
        .Should().Count.AtLeast(1)
        .Should().Count.NoMoreThan(5)
        .Should().Count.Exactly(4)
        .Should().Contain.One(x => x > 2);

    var id = new Guid();
    id.Should().Be.Empty();

    id = Guid.NewGuid();
    id.Should().Not.Be.Empty();

    var date = DateTime.Now;
    date1.Should().Be.Today();

    var str = "";
    str.Should().Be.NullOrEmpty();                

    var one = "1";
    one.Should().Be.ConvertableTo<int>();

    var idString = Guid.NewGuid().ToString();
    idString.Should().Be.ConvertableTo<Guid>();
}

New Post: New Release and Nuget package?

mikeobrien — Tue, 22 May 2012 14:49:21 GMT

Perfect, I'll get on it.

I'm not sure what version they are running, I'll check it out.

New Post: New Release and Nuget package?

erichexter — Tue, 22 May 2012 14:34:07 GMT

yes.. I think I would like to publish the ci to a myfeed feed and then just publish releases to the public nuget.. i assume the codebetter server is using TC 7? so the nuget setup is super easy.

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

New Post: New Release and Nuget package?

mikeobrien — Tue, 22 May 2012 14:23:06 GMT

Awesome! You still interested in getting an automated build/deploy going? If so I can get a script written and get eveything setup on the code better CI server.

New Post: IHideObjectMembers

erichexter — Tue, 22 May 2012 14:15:05 GMT

I think that is a great idea.. we do take pull requests.. i

New Post: New Release and Nuget package?

erichexter — Tue, 22 May 2012 14:13:19 GMT

With the release of Github for Windows.. I talked it over with Tim and we are willing to move to github. I will apply the current pull requests and we can get this thing moved.

Updated Wiki: Home

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

Project Description

PM> install-package should

The following example shows some of the the assertions that are available for objects, booleans, string, and collections.

public void Should_assertions()
{
    object obj = null;
    obj.ShouldBeNull();

    obj = new object();
    obj.ShouldBeType(typeof(object));
    obj.ShouldEqual(obj);
    obj.ShouldNotBeNull();
    obj.ShouldNotBeSameAs(new object());
    obj.ShouldNotBeType(typeof(string));
    obj.ShouldNotEqual("foo");

    obj = "x";
    obj.ShouldNotBeInRange("y", "z");
    obj.ShouldBeInRange("a", "z");
    obj.ShouldBeSameAs("x");

    "This String".ShouldContain("This");
    "This String".ShouldNotBeEmpty();
    "This String".ShouldNotContain("foobar");

    false.ShouldBeFalse();
    true.ShouldBeTrue();

    var list = new List<object>();
    list.ShouldBeEmpty();
    list.ShouldNotContain(new object());

    var item = new object();
    list.Add(item);
    list.ShouldNotBeEmpty();
    list.ShouldContain(item);
}

Should also provides a fluent API. Here are the same assertions as above using the fluent API. Should.Fluent is a direct port of ShouldIt.

public void Should_fluent_assertions()
{
    object obj = null;
    obj.Should().Be.Null();

    obj = new object();
    obj.Should().Be.OfType(typeof(object));
    obj.Should().Equal(obj);
    obj.Should().Not.Be.Null();
    obj.Should().Not.Be.SameAs(new object());
    obj.Should().Not.Be.OfType<string>();
    obj.Should().Not.Equal("foo");

    obj = "x";
    obj.Should().Not.Be.InRange("y", "z");
    obj.Should().Be.InRange("a", "z");
    obj.Should().Be.SameAs("x");

    "This String".Should().Contain("This");
    "This String".Should().Not.Be.Empty();
    "This String".Should().Not.Contain("foobar");

    false.Should().Be.False();
    true.Should().Be.True();

    var list = new List<object>();
    list.Should().Count.Zero();
    list.Should().Not.Contain.Item(new object());

    var item = new object();
    list.Add(item);
    list.Should().Not.Be.Empty();
    list.Should().Contain.Item(item);
};

Here are some additional examples of assertions using the fluent API:

public void Should_fluent_assertions()
{
    var numbers = new List<int> { 1, 1, 2, 3 };
    numbers.Should().Contain.Any(x => x == 1);
    numbers
        .Should().Count.AtLeast(1)
        .Should().Count.NoMoreThan(5)
        .Should().Count.Exactly(4)
        .Should().Contain.One(x => x > 2);

    var id = new Guid();
    id.Should().Be.Empty();

    id = Guid.NewGuid();
    id.Should().Not.Be.Empty();

    var date = DateTime.Now;
    date1.Should().Be.Today();

    var str = "";
    str.Should().Be.NullOrEmpty();                

    var one = "1";
    one.Should().Be.ConvertableTo<int>();

    var idString = Guid.NewGuid().ToString();
    idString.Should().Be.ConvertableTo<Guid>();
}

Updated Wiki: Home

erichexter — Tue, 22 May 2012 14:02:15 GMT

Project Description

PM> install-package should

The following example shows some of the the assertions that are available for objects, booleans, string, and collections.

public void Should_assertions()
{
    object obj = null;
    obj.ShouldBeNull();

    obj = new object();
    obj.ShouldBeType(typeof(object));
    obj.ShouldEqual(obj);
    obj.ShouldNotBeNull();
    obj.ShouldNotBeSameAs(new object());
    obj.ShouldNotBeType(typeof(string));
    obj.ShouldNotEqual("foo");

    obj = "x";
    obj.ShouldNotBeInRange("y", "z");
    obj.ShouldBeInRange("a", "z");
    obj.ShouldBeSameAs("x");

    "This String".ShouldContain("This");
    "This String".ShouldNotBeEmpty();
    "This String".ShouldNotContain("foobar");

    false.ShouldBeFalse();
    true.ShouldBeTrue();

    var list = new List<object>();
    list.ShouldBeEmpty();
    list.ShouldNotContain(new object());

    var item = new object();
    list.Add(item);
    list.ShouldNotBeEmpty();
    list.ShouldContain(item);
}

Should also provides a fluent API. Here are the same assertions as above using the fluent API. Should.Fluent is a direct port of ShouldIt.

public void Should_fluent_assertions()
{
    object obj = null;
    obj.Should().Be.Null();

    obj = new object();
    obj.Should().Be.OfType(typeof(object));
    obj.Should().Equal(obj);
    obj.Should().Not.Be.Null();
    obj.Should().Not.Be.SameAs(new object());
    obj.Should().Not.Be.OfType<string>();
    obj.Should().Not.Equal("foo");

    obj = "x";
    obj.Should().Not.Be.InRange("y", "z");
    obj.Should().Be.InRange("a", "z");
    obj.Should().Be.SameAs("x");

    "This String".Should().Contain("This");
    "This String".Should().Not.Be.Empty();
    "This String".Should().Not.Contain("foobar");

    false.Should().Be.False();
    true.Should().Be.True();

    var list = new List<object>();
    list.Should().Count.Zero();
    list.Should().Not.Contain.Item(new object());

    var item = new object();
    list.Add(item);
    list.Should().Not.Be.Empty();
    list.Should().Contain.Item(item);
};

Here are some additional examples of assertions using the fluent API:

public void Should_fluent_assertions()
{
    var numbers = new List<int> { 1, 1, 2, 3 };
    numbers.Should().Contain.Any(x => x == 1);
    numbers
        .Should().Count.AtLeast(1)
        .Should().Count.NoMoreThan(5)
        .Should().Count.Exactly(4)
        .Should().Contain.One(x => x > 2);

    var id = new Guid();
    id.Should().Be.Empty();

    id = Guid.NewGuid();
    id.Should().Not.Be.Empty();

    var date = DateTime.Now;
    date1.Should().Be.Today();

    var str = "";
    str.Should().Be.NullOrEmpty();                

    var one = "1";
    one.Should().Be.ConvertableTo<int>();

    var idString = Guid.NewGuid().ToString();
    idString.Should().Be.ConvertableTo<Guid>();
}

Updated Wiki: Home

erichexter — Tue, 22 May 2012 14:01:44 GMT

Project Description

PM> install-package should

The following example shows some of the the assertions that are available for objects, booleans, string, and collections.

public void Should_assertions()
{
    object obj = null;
    obj.ShouldBeNull();

    obj = new object();
    obj.ShouldBeType(typeof(object));
    obj.ShouldEqual(obj);
    obj.ShouldNotBeNull();
    obj.ShouldNotBeSameAs(new object());
    obj.ShouldNotBeType(typeof(string));
    obj.ShouldNotEqual("foo");

    obj = "x";
    obj.ShouldNotBeInRange("y", "z");
    obj.ShouldBeInRange("a", "z");
    obj.ShouldBeSameAs("x");

    "This String".ShouldContain("This");
    "This String".ShouldNotBeEmpty();
    "This String".ShouldNotContain("foobar");

    false.ShouldBeFalse();
    true.ShouldBeTrue();

    var list = new List<object>();
    list.ShouldBeEmpty();
    list.ShouldNotContain(new object());

    var item = new object();
    list.Add(item);
    list.ShouldNotBeEmpty();
    list.ShouldContain(item);
}

Should also provides a fluent API. Here are the same assertions as above using the fluent API. Should.Fluent is a direct port of ShouldIt.

public void Should_fluent_assertions()
{
    object obj = null;
    obj.Should().Be.Null();

    obj = new object();
    obj.Should().Be.OfType(typeof(object));
    obj.Should().Equal(obj);
    obj.Should().Not.Be.Null();
    obj.Should().Not.Be.SameAs(new object());
    obj.Should().Not.Be.OfType<string>();
    obj.Should().Not.Equal("foo");

    obj = "x";
    obj.Should().Not.Be.InRange("y", "z");
    obj.Should().Be.InRange("a", "z");
    obj.Should().Be.SameAs("x");

    "This String".Should().Contain("This");
    "This String".Should().Not.Be.Empty();
    "This String".Should().Not.Contain("foobar");

    false.Should().Be.False();
    true.Should().Be.True();

    var list = new List<object>();
    list.Should().Count.Zero();
    list.Should().Not.Contain.Item(new object());

    var item = new object();
    list.Add(item);
    list.Should().Not.Be.Empty();
    list.Should().Contain.Item(item);
};

Here are some additional examples of assertions using the fluent API:

public void Should_fluent_assertions()
{
    var numbers = new List<int> { 1, 1, 2, 3 };
    numbers.Should().Contain.Any(x => x == 1);
    numbers
        .Should().Count.AtLeast(1)
        .Should().Count.NoMoreThan(5)
        .Should().Count.Exactly(4)
        .Should().Contain.One(x => x > 2);

    var id = new Guid();
    id.Should().Be.Empty();

    id = Guid.NewGuid();
    id.Should().Not.Be.Empty();

    var date = DateTime.Now;
    date1.Should().Be.Today();

    var str = "";
    str.Should().Be.NullOrEmpty();                

    var one = "1";
    one.Should().Be.ConvertableTo<int>();

    var idString = Guid.NewGuid().ToString();
    idString.Should().Be.ConvertableTo<Guid>();
}

New Post: New Release and Nuget package?

taylonr — Sat, 19 May 2012 20:48:56 GMT

I second Mike. I had a similar thought.

New Post: New Release and Nuget package?

mikeobrien — Sun, 06 May 2012 17:00:57 GMT

erichexter wrote:
I can put together a new release on nuget... It is easier for me to just script out the nuget push in our ci server than to manually update the releases on the codeplex project. I have so many OSS projects going right now, I am running out of bandwidth to keep it all going.

That being said, if someone would like to act as a release manager for this project, I would certainly appreciate the help!

What would you think about moving the source to github and we could setup an automated build (And nuget push) on the codebetter CI? I'd be willing to handle this if it's ok w/ you.

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.

New Post: Review after playing with it for a while

Vaccano — Fri, 14 Oct 2011 18:53:23 GMT

This library is great. I really like that I don't have to type open and close parens () for every part of the assertion.

One thing that is missing is that the "Error Message" needs to be more brief when an assertion fails. For example: this is a current error message:

   Test method IntegrationTests.IntegrationOrderTests.SaveNewOrders_NormalOrders_NoErrors threw exception:
   Should.Core.Exceptions.EqualException: Assert.Equal() Failure
   Expected: 1
   Actual:   2

I know what method failed already. What I really want to see in the Error Message is this:

Expected: 1 Actual: 2

That way I don't have to open up the results of every test that failed to see that the assertion failed.