Test Driving User Interfaces

Test Driving business and persistence logic has been proven to be an effective technique for incremental design, reduced complexity, and easy automated regression testing. Many teams struggle with how to achieve these same benefits for User Interfaces. The traditional notion is that a UI is too fragile and hard to test until it is already built.

This session will consist of a brief explanation of the Page Object pattern, followed by a live coding demo showing the integration of Cucumber-JVM with Selenium via Page Objects. Code is available at https://github.com/nhajratw/test-driving-user-interfaces

Transcript

1. Test Driving User Interfaces Nayan Hajratwala @nhajratw nayan@chikli.com Jeremy Anderson @jeremydanderson jeremy@code-adept.com 1 Monday, January 14, 13
2. Testing Pyramid UI Customer Integration Programmer Unit / Isolation Programmer 2 Monday, January 14, 13
3. UI Testing • Brittle • Slow 3 Monday, January 14, 13
4. UI Testing • Brittle • Slow 4 Monday, January 14, 13
5. What we’re not test driving • User Experience • To the pixel placement (though possible) 5 Monday, January 14, 13
6. Page Object • An object that represents a page or a section of a page for testing. • A single source for knowledge about the page. 6 Monday, January 14, 13
7. The Stack Java Cucumber-JVM Selenium WebDriver 7 Monday, January 14, 13
8. Alternatives • Java: Roll your own • Groovy: Geb • Ruby: page-object gem 8 Monday, January 14, 13
9. Nayan Hajratwala @nhajratw nayan@chikli.com Jeremy Anderson @jeremydanderson jeremy@code-adept.com •https://github.com/nhajratw/test-driving-user-interfaces •https://github.com/punkisdead/CodeMashBaconTracker 9 Monday, January 14, 13