How to implement UI testing without shooting yourself in the foot

I’m currently interviewing lots of teams that have implemented acceptance testing for my new book. A majority of those interviewed so far have at some point shot themselves in the foot with UI test automation. After speaking to several people who are about to do exactly that at the Agile Acceptance Testing Days in Belgium a few weeks ago, I’d like to present what I consider a very good practice for how to do UI test automation efficiently. Continue reading

Are tools necessary for acceptance testing, or are they just evil?

While doing research for my new book, I was very surprised to find out that Jim Shore gave up on acceptance testing. I use his “describe-demonstrate-develop” process description all the time in my workshops, so I guess I better stop doing that. Jim Shore wrote:

My experience with Fit and other agile acceptance testing tools is that they cost more than they’re worth. There’s a lot of value in getting concrete examples from real customers and business experts; not so much value in using “natural language” tools like Fit and similar.

The two failure patterns that Shore describes in his post are falling back on testers to write everything and merging acceptance and integration tests. I’ve experienced both of these myself, and it seems that they are common in general. We discussed both during the top 10 ways to fail with acceptance testing openspace session at CITCON Europe last year. However, there are good ways to solve both problems. Continue reading

Agile acceptance testing tools roundup videos

Here are the videos from the Agile acceptance testing tools round-up event held on May 27th at Skills Matter in London.


David Peterson on Concordion. Grab the slides.



Elizabeth Keogh on JBehave2



My presentation on FitNesse, TextTest and Robot Framework.
You can grab the slides or read the Robot framework review.