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...

I’ve just published my 800th post!

Can’t really understand that. I know that some of them haven’t been all that great but there’s some nuggets of information in there. At least for me.

That’s how I started to blog: to make myself write stuff down to remember and formalize my knowledge.

800 posts, six years, 163 000 pageviews. That’s not a lot for many blogs out there but it means a lot to me.

Thank you for reading my blog. Even though I started to write it for myself - comments and reactions is  what kept me going on for 6 years! I cannot promise 6 more but right now I’m on a roll.

If your doing specification by example or BDD you will soon realize that the tooling still points towards developers. WIth that I mean, that Cucumber and SpecFlow allows you to write your (executable) specifications in plain text, but you still check it into the source repository. This is of course a good thing since you’d want to version the specification with your code - but it also effectively hides it and keeps the spec out of reach for any non-developing member of the team.

Make no mistake here: the .feature-file is the master and original. That’s how it should be since it’s versioned together with the code. But we want everyone in the team to be able to read the specifications and see the test result easily. So we generate documentation off the .feature-files.

Pickles is a nice OSS framework that helps you solve...

On a Sunday night a got a mail that asked me to do a presentation tomorrow. New client. Want to put best foot forward. :) So I threw one together and here’s the run down of it. Thinking of recording it and put it up somewhere too.

Lean Coffee is a way to hold meetings and gathering that allows for free discussions while still keeping some structure to it. It resembles Open Space Technology but is much easier to set up and run, and often run in small groups. Even thought the concept is called Lean Coffee is suitable for discussing most any subject and topics.

Lean Coffee started in Seattle in 2009. Jim Benson and Jeremy Lightsmith first Lean Coffee group has inspired a lot of others around the globe. I’ve taken part in the one in Stockholm LeanKaffeSump quite a few time, but have...

I have a new coaching assignment at Tradera which is the Swedish branch of Ebay. I’ve been there about 30 hours during the last three years, mostly doing presentations and courses. In a way it feels like I’ve been part in what they have done, but only as a bystander. This gig looks like a lot of fun and I’ve always been impressed by the technical excellence there and the willingness to adopt new things and change.

I was thrown right in at the deep end as they were about to reorganize their big team (30-40 people) into 5 smaller teams with particular features to look after. The first thing they wanted help with was some input around HOW to go about organizing this. And make no mistake - they we’re well on their way doing this in a excellent way already. I merely supplied some confirmation and...

As always it’s hard to boot up all processes in a new year. The blogging process apparently was down prioritized by my internal product owner. Well - he’ll have to stand back: I’m on it again.

For quite some time I have pondered constraints. They fascinates me quite a lot. Especially the ones that we take upon ourselves. In fact: I would go so far as to say that nothing good comes from having no constraints. Let’s go back a bit in my thoughts and see if I can clarify why.

In reality this post is just a couple of examples of self-imposed constraints and what good they can have.

Toyota and TPS

First let’s stop, again, at Toyota. Why did they invent TPS (Toyota Production System)? What drove them there? It’s a quest that they’ve been on since the 50-ies and never will be done with.

I have a couple of slow weeks before my next assignment starts for real, so as an early Christmas gift Aptitud and I thought that we could give away some presentations for free.

Please contact me on marcusoftnet at gmail or @marcusoftnet if you are interested in hearing any of the presentations below. No charge (saved any travel costs outside Stockholm… and the obligatory cup of strong, black coffee) and no strings attached.

[UPDATED] I have now booked my calendar to a suitable level (almost full). The response on this post was just overwhelming and I got 7 different gigs including a whole day at one company and a contact in Brasil (!). Might do this again. Longing to be bored again.

These are the presentations that I can give with an hours notice: