Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Selenium Design Patterns and Best Practices
  • Toc
  • feedback
Selenium Design Patterns and Best Practices

Selenium Design Patterns and Best Practices

By : Kovalenko
3.9 (11)
close
Selenium Design Patterns and Best Practices

Selenium Design Patterns and Best Practices

3.9 (11)
By: Kovalenko

Overview of this book

Selenium WebDriver is a global leader in automated web testing. It empowers users to perform complex testing scenarios with its simple and powerful interface. This guide will provide you with all the skills you need to successfully create a functional Selenium test suite. Starting from the very beginning of the Selenium IDE, this book will show you how to transition into a real programing language such as Ruby or Java. You will quickly learn how to improve your code quality with refactoring and the skills needed to plan for the future development of your website to future-proof your test suite. With ample test examples running against a life-like e-commerce store and detailed step-by-step code review and explanations, you will be ready to test any challenge web developers might throw your way. This book is intended for anyone who wants to create a test suite that is easy to maintain by expanding your knowledge until you feel truly confident and comfortable with Selenium.
Table of Contents (11 chapters)
close
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Free Chapter
1
1. Writing the First Test
1. 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
2. The Spaghetti Pattern
2. 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
3. Refactoring Tests
chevron up
3. Refactoring Tests
Refactoring tests
The DRY testing pattern
The Hermetic test pattern
Creating generic DRY methods
The random run order principle
Summary
4
4. Data-driven Testing
4. 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
5. Stabilizing the Tests
5. 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
6. Testing the Behavior
6. 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
7. The Page Objects Pattern
7. 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
8. Growing the Test Suite
8. Growing the Test Suite
Strategies for writing test suites
Continuous Integration
Frequently Asked Questions
Summary
9
A. Getting Started with Selenium
A. Getting Started with Selenium
Setting up the computer
Understanding test class naming
Summary
10
Index
Index

Creating generic DRY methods

At this point, our test is no longer recognizable compared to what it was at the beginning of the chapter. Before we wrap it up, let's talk about the generic action used all through our tests. Throughout the test code, we use some common methods to perform actions such as clicking or typing text into a text field. These chained methods look something like this:

Creating generic DRY methods

What if we refactor these methods a little further and create some generic private methods that can be used in a much simpler way? Let's start with the most common method used, @selenium.find_element, and create a generic find_element method:

Creating generic DRY methods

Our find_element method now accepts an element identifier and an optional strategy parameter. If the strategy is not specified, it will default to the CSS selector.

Note

More information about element locator strategies can be found in Chapter 2, The Spaghetti Pattern.

Now let's add two new methods that use our local find_element method to click and type...

End of Section 5
Next Section
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete