The document discusses acceptance testing frameworks, including what they are, why they are worthwhile, and what should go into one. It defines an acceptance testing framework as one that defines the format for expressing expectations, drives the application under test, executes the tests, and reports results. Frameworks help avoid issues like brittle tests and performance problems that commonly occur with tools like Selenium. Effective frameworks have components like a runner, integration, configuration, reporting, logging, and a domain-specific language. The real value is realized by integrating frameworks with continuous integration to provide timely test results. Several open source and commercial frameworks are described.
4. Elizabeth Hendrickson says...
1. Defines the format in which to
express expectations
2. Creates a mechanism to hook into, or
drive, the application under test
3. Executes the tests
4. Reports the results
[link]
7. 1 - Record tests with Selenium IDE
2 - End up with a brittle suite of tests
3 - Export to code, get them working
4 - Rewrite them so they're DRY
5 - Scale, hit performance issues
6 - Monkey-patch as you go
A - Ignore it and go back to manual testing
B - Throw it out and rewrite
Standard Selenium Evolution
17. Recap
● An 'acceptance testing framework' that is
built for successful Selenium has a lot of
parts
● A framework will help you get started, grow,
and avoid pitfalls
● There are many "frameworks" (both open
source and commercial)
● But there are few that come with everything
you need out of the box
● The real value comes from using it within
your development workflows
19. Additional Resources
Selenium HQ's outdated framework page
Agile Alliance Functional Testing Tools
spreadsheet (outdated-ish)
wiki (should be the record of truth)
List of available Selenium Resources
blog post on arrgyle.com
SF Selenium Meetup's Testing Tool Demo Night videos