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?
How do these tests relate to the acceptance tests on the back of the story cards? Are there other kinds of acceptance tests, perhaps within a hierarchy, which don't focus on the user?
Previous Topic
