Acceptance Tests are Executable System Specification

Many, many people think that Test First approach is not working and not intuitive at all (especially for acceptance tests). They have a point when say “How could we test something if we don’t have implementation and even system specification?”. Yes, if you don’t have requirements, you can’t test. But they don’t understand that acceptance tests ARE that spec. It is not wise to artificially separate User Stories from Acceptance Tests. They may be in one place and make up the spec. And even more, it should be executable spec. FIT is one of the closest solution to make spec executable. The tricky thing is to make acceptance tests creation as informal as possible, while keeping them executable. FIT provide a mix: you may write some informal sentences in Word doc, then create a table that will contain test harness. While the first part is simple for customer, the second is not and should be created together with developer, QA or someone who have experience with FIT.

Is it possible to make acceptance tests creation process simpler? Less formal? Intuitive? That’s an interesting challenge!

One thought on “Acceptance Tests are Executable System Specification”

  1. Kind of an old post I see, but anyway… check out Selenium if hou haven’t already: From their site: “Selenium is a test tool for web applications. Selenium tests run directly in a browsers, just as real users do. And they run in Internet Explorer, Mozilla and Firefox on Windows, Linux and Macintosh…”


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s