Nancy.Testing - test-dialogues with Requests and Response

Posted by Marcus Hammarberg on January 31, 2013
This is the third post in my series on Nancy.Testing. It will focus a lot of the Browser and the Response object. Together with the Browser (and it's ConfigurableBootstrapper) these objects makes up the entirety of the Nancy.TestingFramework.

Let's do the logo thing again, shall we?

The other posts can be found here:
  1. Intro to testing with Nancy
  2. The Configurable bootstrapper
  3. The Browser and Response objects (this post)
  4. Hat and shoeless testing with Simple.Data
  5. SpecFlow and Nancy
By now you're probably just looking for the code so let's dive right in.

Browser

The Browser object is the one that you use to issue requests to the site you're testing. Most of the Browser configuration is done through the ConfigurableBootstrapper and let's not go over that again.

But the Browser has a couple of other tricks up it's sleeve to. With each method that you can use to issue HTTP Requests (Get, Post, Delete, Put, Options etc) there's configuration to be done to. Here's a real simple example that shows how you can configure your tests to do Https-requests:
By now you recognize the pattern with configuring your object through a lambda (with => with.WhatHaveYou). On row 8 and 21 we configure the Get-request to use a Http or an Https-request, that our module under test recognize.

There's loads more you can do with each Http-request, the most commonly used I would bet is the Form-posting abilities. Here's one example:
As you can see from lines 11 and 12 it's quite easy to populate a form to post.
This example also showed off model binding in Nancy (line 28). In a internal class, in the test, no references to a web framework. Cool, huh?

In much the same manner you can send in values through the query string  in cookies or via headers. It's very similar code and I've created a sample here:
The other ways to send data this way are shown in comments, and you can see my code here.

That leaves some special things (expect for AjaxRequest that's really special and I'll leave for you to examine on your own). First out is to create your HTTP Body on your own. Here's an example of doing that:

This gives you very fine-grained control of the content of the Body, and as you can see from this example (ripped directly from the Nancy.Testing.Test code) we're sending in some JSon in the body on line 11. That's handily taken care of by the handler and bound to our model (line 25). 

You can also send JSon directly in the body. Very conveniently Nancy.Testing also supplies a method for converting a class to Json for you:

Let's now go to the other side of the request and take a closer look at the Response-object and see the help that Nancy.Testing gives us there. It's plenty!

Response

There's loads of interesting stuff on the response object. First you can, of course, access all the properties and assert that expected data was returned. Here's a couple of examples:

Nothing really strange and suprising there. You can access the properties of the Response just as expected and do your own assertions against them. In these example I'm simply accessing the Headers and Cookies collection. The rest of them behave in the same manner and are:

  • Context - which gives you access to the NancyContext and properties as: 
    • The Parameters collection
    • The CurrentUser
    • NegotiationContext
    • ModelValidationResult
    • ViewBag
  • The Body itself which I'll talk about later
  • The HTTP status code

Other Response methods

There's also some special methods that checks for redirects:

And also for getting the Body into different formats and even deserilize it into model objects:

Body assertions

The Body property is a little gem in itself in that it has all the elements of the -tag as keys (it's a DynamicDictionary). Not only that - you can also search these with normal CSS Selectors. This gives a very nice experience checking for presence of tags, it's content and id etc. I've put together some examples here:
But hey - there's more: the error messages are to die for. Here's one:
"The expected value 'A second message with isd' was not a sub-string of the actual value 'A second message with id'."
Tester nirvana - right there! Thank the creators!

Summary

Probably broke my long-blog-post-record there. So I'll end it now. 
A lot of goodies in here for you to deep-dive in. Get my full code here


Published by Marcus Hammarberg on Last updated