Why Your Selenium Tests are so Dang Brittle, and What to Do About It
- 4,039 views
If you are writing automated through-the-GUI tests for a web application, you are in danger of creating tests that are more expensive to maintain than they are worth. With well-factored Selenium RC ...
If you are writing automated through-the-GUI tests for a web application, you are in danger of creating tests that are more expensive to maintain than they are worth. With well-factored Selenium RC tests running in Junit or TestNG, you can keep your abstraction layers or "Lingos" -- small bounded bits of slang for discrete parts of the object model -- separate, thereby reducing the maintenance costs of your tests, and improving your sanity.
This presentation is from a technical track webinar on:
•How and why automated web app code gets so dang brittle
•Why the expressiveness, readability, and fluency of your test code is so important to its maintenance cost
•Some basic, useful OOD patterns for writing very expressive web app tests using Selenium RC, in Java and in C#/.NET
•Some useful OOD principles to guide your design decisions, like keeping modules small, the SRP, DRY, "Lingos", and "Lingual Design"
•Some OOD principles worth violating, frequently, when writing automated test code, because it's just very different from application code
•How and why to prefer element locators like Id and Value attributes to xPath; how to keep xPath least brittle
•An introduction to Domain Specific Languages (DSLs) built on top of Selenium RC, using FitNesse
•An introduction to "fluent" Selenium RC testing using Scala
Prerequisites include experience with Java or C#, and ideally some basic OOD familiarity (inheritance, composition, encapsulation, polymorphism).
To view or download a replay of the event (WMV format), which included live demonstrations, please visit: http://www.pillartechnology.com/content/webinardetail/id/16
- Total Views
- Views on SlideShare
- Embed Views