2. Who is this lady?
http://passionatetester.com
• Currently Tester at 42 Lines
• Software testing specialist for 10 years
• One-time developer
• Test team builder
• Maintainer on .net Selenesse open source project
3. What do all of these words mean?
• Executable Specifications?
• FitNesse?
• Selenium?
4. The Test Automation Pyramid
Created by Brian Marick, used in the book Agile Testing, by Lisa Crispin and Janet Gregory
5. Ever seen this before?
• What’s developed isn’t what the customer wanted
• Buggy product, lots of rework
• Some team members lack domain knowledge, don’t
understand context of features
• Business team doesn’t trust development team to
complete tasks well/ on time
6. Business vs Dev Cage
Match
That’s not
what I
asked for!
SCOPE
CREEP!
7. How can we minimize this?
• Start by getting the right people together: usually, a
customer/business person, developer, tester
• Talk through the details, come to a common vocabulary
• Specify as many examples as make sense
8. Benefits of this approach
When examples are written in a way that can be run as
tests:
•Miscommunications due to “playing telephone” are
minimized
•Everyone is on the same page very early
•Bugs are prevented
10. Gotchas in automation
Test automation in the browser presents challenges:
•Locating elements – using CSS Selectors
•Synchronizing with the web server – Waiting for
elements to appear
•Maintaining over time – creating common actions
12. FitNesse framework
• Web page, accessible to all team members
• Wiki markup is easy to learn
• Plain text, can be checked in with source code
• Executes tests and reports results back
• Shows test execution history