Book Image

Selenium Design Patterns and Best Practices

By : Dima Kovalenko
Book Image

Selenium Design Patterns and Best Practices

By: Dima Kovalenko

Overview of this book

Related Content you might be interested in

Current Title:

Small book image
Selenium Design Patterns and Best Practices
Dima Kovalenko
Sep, 2014 | 270 pages
No titles found
Table of Contents (18 chapters)
Selenium Design Patterns and Best Practices
Selenium Design Patterns and Best Practices
Credits
Credits
Foreword
Foreword
About the Author
About the Author
Acknowledgments
Acknowledgments
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Writing the First Test
Writing the First Test
Choosing Selenium over other tools
The Record and Playback pattern
Getting started with the Selenium IDE
Understanding Selenium commands
Comparing Ruby to Selenese
Comparing Selenium commands in multiple languages
Writing a Selenium test in Ruby
Summary
2
The Spaghetti Pattern
The Spaghetti Pattern
Introducing the Spaghetti pattern
Testing the product review functionality
Reasons for failures
The Chain Linked pattern
The Big Ball of Mud pattern
Summary
3
Refactoring Tests
Refactoring Tests
Refactoring tests
The DRY testing pattern
The Hermetic test pattern
Creating generic DRY methods
The random run order principle
Summary
4
Data-driven Testing
Data-driven Testing
Data relevance versus data accessibility
Hardcoding input data
Introducing test fixtures
Using an API as a source of fixture data
Using data stubs
The default values pattern
Summary
5
Stabilizing the Tests
Stabilizing the Tests
Engineering the culture of stability
Waiting for AJAX
Waiting for JavaScript animations
The Action Wrapper pattern
The Black Hole Proxy pattern
Test your tests!
Summary
6
Testing the Behavior
Testing the Behavior
Behavior-driven Development
Testing the shopping cart behavior
Introducing Cucumber
Running the Cucumber suite
The write once, test everywhere pattern
Testing a mobile site
Testing the purchase API
Summary
7
The Page Objects Pattern
The Page Objects Pattern
Understanding objects
The Page Objects pattern
Creating a Page Objects framework
Running tests with the Page Objects framework
The test tool independence pattern
The right way to implement Page Objects
Summary
8
Growing the Test Suite
Growing the Test Suite
Strategies for writing test suites
Continuous Integration
Frequently Asked Questions
Summary
Getting Started with Selenium
Getting Started with Selenium
Setting up the computer
Understanding test class naming
Summary
Index
Index

The write once, test everywhere pattern

Jeff Roggers and Kristan Vingrys initially developed the write once, test everywhere pattern while working at ThoughtWorks. The concept centers on taking advantage of shared behavior between multiple implementations of one application. For example, it should be possible to purchase a product from our website no matter whether the user is using our full website, the mobile version, or native mobile application. If the feature definitions are well written, the steps used to implement the test can be interchangeable.

Note

The write once, test everywhere pattern is also known as the pluggable test pattern, since we can plug the implementation of tests into different contexts. As we change the context from the desktop website to mobile to API tests, we plug in the correct implementation.

Advantages of the write once, test everywhere pattern

The write once, test everywhere pattern has several advantages going for it; here is a list of a few of them:

  • Foresight...

Previous Section
End of Section 6
Next Section