Sign In Start Free Trial

Selenium Design Patterns and Best Practices

By : Kovalenko

3.9 (11)

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.

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. 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. 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. Refactoring Tests

3. 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

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. 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. 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. 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. Growing the Test Suite

8. Growing the Test Suite

Strategies for writing test suites

Continuous Integration

Frequently Asked Questions

Summary

A. Getting Started with Selenium

A. Getting Started with Selenium

Setting up the computer

Understanding test class naming

Summary

Index

Index

Customer Reviews

3.9 (11)

5 star

36.4%

4 star

27.3%

3 star

27.3%

2 star

9.1%

1 star

0

Conventions

In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "You can even open the search_test.html file in your web browser and see how it looks!"

A block of code is set as follows:

more_info_buttons = special_items.collect do |special_item|
  special_item.find_element(:class, "more-info")
end

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

require 'rubygems'
require 'selenium-webdriver'

selenium = Selenium::WebDriver.for(:firefox)
selenium.get("http://awful-valentine.com/")
selenium.find_element(:id, "searchinput").clear
selenium.find_element(:id, "searchinput").send_keys("cheese")
selenium.find_element(:id, "searchsubmit").click
selenium.quit

Any command-line input or output is written as follows:

ruby run_tests.rb

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "Click on Install Now when it becomes clickable after several seconds."

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.

Search

Your notes and bookmarks