tpierrain/nfluent-web

(alpha) NFluent.Web is an extension library to NFluent for web-related tests. NFluent is an ergonomic assertion library which aims to fluent your .NET TDD experience (based on simple Check.That() assertion statements). NFluent aims your tests to be fluent to write (with an happy 'dot' auto completion experience), fluent to read (i.e. as close as possible to plain English expression), but also fluent to troubleshoot, in a less-error-prone way comparing to the classical .NET test frameworks. NFluent is also directly inspired by the awesome Java FEST Fluent assertion/reflection library (http://fest.easytesting.org/)

nfluent-web's Issues

Find a way to chain multiple assertions on the same HttHeader

To be able to write assertion like this:

Check.That(response).StatusCodeEqualsTo(HttpStatusCode.OK)
.And.HasHeader(HttpResponseHeader.CacheControl)
.And.HasHeader("X-Frame-Options").Which.Contains("SAMEORIGIN").And.StartsWith("SAME").And.EndsWith("ORIGIN")
.And.IsGZipEncoded().And.Contains("Google")
.And.IsInstanceOf()
.And.IsNotInstanceOf()
.And.IsEqualTo(response).And.IsNotEqualTo("Batman");

Refactor the error messages of NFluent.Web

So that they are aligned with the NFluent core ones.

Migrate NFluent-Web to the new extensibility model suggested by Rui

Once the migration of the NFluent core library to this new model will be achieved.

Find a way for the IIHttpHeaderFluentAssertion interface to support the same methods as the IStringFluentAssertion interface (StartsWith(), EndsWith(), Contains(), etc)

Study whether we could leverage or not on a common implementation among the HttpHeaderFluentAssertion and the StringFliuentAssertion classes (only their return value types will differ).

Make the IHttpHeaderFluentAssertion.Contains(string expected) method accepting multiple values as argument instead

From:

IChainableFluentAssertion Contains(string expected);

to:

IChainableFluentAssertion Contains(params string[] values);