I want to play more with the combination of
behaviour-driven development and
Selenium IDE . Stuff isn't clear in my head yet
and I'm not entirely sure what I'm aiming for. Maybe it's that,
given my interest in usability and interaction design, I want
greater emphasis on the user in our acceptance tests.
Am I seeing a Selenium test demonstrate the achievement of a
user's goal, broken down into the user's actions expressed in plain
English that map, under-the-hood, to Selenium commands?
Questions I'm asking myself: How do these tests relate to the
acceptance tests on the back of the story cards? Are they the only
tests on the back of the card? If they're not user-focused their
'internal', right? Are there other kinds of Selenium-based
acceptance tests, perhaps within a hierarchy, which don't focus on
the user? Are these aceptance tests?
Um ...
Thursday, 13 August 2009
Thinking out loud about users, behaviour and acceptance tests
Posted by Simon Baker - Permalink
1 Comment
If you want some inspiration look at Thoughtworks Twist which is Selenium tests joined together to make up a test case you'd see on the back of a card