book

Selenium Design Patterns and Best Practices

Name: Selenium Design Patterns and Best Practices
Author: Dima Kovalenko
ISBN: 9781783982707

by Dima Kovalenko

September 2014

Intermediate to advanced

270 pages

6h 1m

English

Packt Publishing

Read now

Unlock full access

Selenium Design Patterns and Best Practices
Table of Contents
Selenium Design Patterns and Best Practices
Credits
Foreword
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Support files, eBooks, discount offers, and moreWhy subscribe?Free access for Packt account holders
Preface
What this book covers

What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Downloading the example codeErrataPiracyQuestions
1. Writing the First Test
Choosing Selenium over other toolsRight tool for the right jobPriceOpen sourceFlexibility
The Record and Playback pattern
Advantages of the Record and Playback patternDisadvantages of the Record and Playback pattern
Getting started with the Selenium IDE
Installing the Selenium IDERecording our first testSaving the test
Understanding Selenium commands
Reading Selenese
Comparing Ruby to Selenese
Comparing Selenium commands in multiple languages
Writing a Selenium test in Ruby
Introducing Test::UnitIntroducing assertsInteractive test debugging
Summary
2. The Spaghetti Pattern
Introducing the Spaghetti patternAdvantages of the Spaghetti patternDisadvantages of the Spaghetti pattern
Testing the product review functionality
Starting a product review testLocating elements on the pageUsing a browser's element inspectorIntroducing locator strategiesUsing advanced locator strategiesUsing the absolute pathUsing the relative pathWriting locator strategy codeUsing chained selector strategy methodsUsing the CSS selectorUsing XPathImplementing clicks and assertionsDuplicating the product review test
Reasons for failures
The Chain Linked pattern
The Big Ball of Mud pattern
Summary
3. Refactoring Tests
Refactoring tests
The DRY testing pattern
Advantages of the DRY testing patternDisadvantages of the DRY testing patternMoving code into a setup and teardownRemoving duplication with methodsRemoving external test goalsUsing a method to fill out the review formReviewing the refactored code
The Hermetic test pattern
Advantages of the Hermetic test patternDisadvantages of the Hermetic test patternRemoving test-on-test dependenceUsing timestamps as test dataExtracting the remaining common actions to methodsCreating a new review with a single method callReviewing the test-on-test dependency refactoring
Creating generic DRY methods
Refactoring with generic methods
The random run order principle
Advantages of the random run order principleDisadvantages of the random run order principle
Summary
4. Data-driven Testing
Data relevance versus data accessibility
Hardcoding input data
Hiding test data from testsChoosing the test environment
Introducing test fixtures
Parsing fixture dataUsing fixture data in the testsUsing fixtures to validate productsTesting the remaining productsMultiple test modelsA single test modelImplementing multiple test modelsMaking test failures more expressive
Using an API as a source of fixture data
Using data stubs
The default values pattern
Advantages of the default values patternDisadvantages of the default values patternMerging the default values pattern and the faker libraryImplementing faker methodsUpdating the comment test to use default values
Summary
5. Stabilizing the Tests
Engineering the culture of stabilityRunning fast and failing fastRunning as often as possibleKeeping a clean and consistent environmentDiscarding bad code changesMaintaining a stable test suite
Waiting for AJAX
Testing without AJAX delaysUsing explicit delays to test AJAX formsImplementing intelligent delays
Waiting for JavaScript animations
The Action Wrapper pattern
Advantages of the Action Wrapper patternDisadvantages of the Action Wrapper patternImplementing the Action Wrapper pattern
The Black Hole Proxy pattern
Advantages of the Black Hole Proxy patternDisadvantages of the Black Hole Proxy patternImplementing the Black Hole Proxy pattern
Test your tests!
Summary
6. Testing the Behavior
Behavior-driven DevelopmentAdvantages of BDDDisadvantages of BDD
Testing the shopping cart behavior
Describing shopping cart behaviorWriting step definitionsIs BDD right for my project?
Introducing Cucumber
Feature filesStep definition filesThe configuration directoryCucumber.ymlenv.rb
Running the Cucumber suite
The write once, test everywhere pattern
Advantages of the write once, test everywhere patternDisadvantages of the write once, test everywhere pattern
Testing a mobile site
Updating the Selenium wrapperMoving step definition filesUpdating the Cucumber profile and tagging testsRunning and fixing incompatible steps
Testing the purchase API
Summary
7. The Page Objects Pattern
Understanding objectsDescribing a literal objectObject propertiesObject actionsObjects within objectsDescribing a programming objectDescribing a web page with objects
The Page Objects pattern
Advantages of the Page Objects patternDisadvantages of the Page Objects pattern
Creating a Page Objects framework
Creating a page super classImplementing sidebar objectsImplementing the SidebarCart classAdding Self Verification to pagesImplementing individual page classesIncreasing the number of sidebar objects as the website grows
Running tests with the Page Objects framework
Using Page Objects in the Test::Unit frameworkUsing Page Objects in different testing frameworksLooking at the Cucumber implementationLooking at the RSpec implementation
The test tool independence pattern
Advantages of the test tool independenceDisadvantages of the test tool independence
The right way to implement Page Objects
Making pages smarter than testsMaking tests smarter than pagesUsing modules instead of inheritancePlacing logic in Page Objects
Summary
8. Growing the Test Suite
Strategies for writing test suitesDifferent types of testsThe smoke test suiteThe money path suiteNew feature growth strategyBug-driven growth strategyThe regression suiteThe 99 percent coverage suite
Continuous Integration
Managing the test environments and nodesDeploying new buildsCI environment managementBuild node managementConfiguration management systemVirtualizationSelenium GridUnderstanding standalone and grid modesJsonWire protocolStandalone modeGrid modeInstalling Selenium GridUsing Selenium GridSelenium Grid ExtrasChoosing the CI toolDecoupling tests from tools
Frequently Asked Questions
How to test on multiple browsers?ProblemPossible solutionsLocalhost testingSetting up Selenium GridSetting up SauceLabs GridWhich programming language to write tests in?Should we use Selenium to test the JS functionality?ProblemPossible solutionWhy should I use a headless browser?Possible solutionPhantomJSWhich BDD tool should I use on my team?ProblemPossible solutionsCan I use Selenium for performance testing?ProblemPossible solutions
Summary
A. Getting Started with Selenium
Setting up the computerUsing Command Line InterfaceUsing the terminal on WindowsUsing MS-DOSUsing PowerShellUsing the terminal emulatorUsing the terminal on Mac OS XUsing the terminal on LinuxConfiguring the Ruby runtime environmentInstalling RubyInstalling the selenium-webdriver gemInstalling Firefox
Understanding test class naming
Naming filesNaming classesUnderstanding the namespaceShowing object inheritance
Summary
Index

Content preview from Selenium Design Patterns and Best Practices

Continuous Integration

The most amazing test suite ever written is useless if it sits on someone's laptop and is never executed! Having our tests in CI is not only beneficial to the quality of the application, but it is also beneficial to the quality of the test suite itself. By executing the test suite dozens of times a day we can discover test instabilities, which occur once in a while.

There are five components to setting up a Continuous Integration system. They are listed in order of importance here:

Test environment: In order to execute the tests, we need to have an application we are trying to test. Without a test environment, the tests are just pieces of code that cannot be executed. We talked about different types of test environments in ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Selenium Framework Design in Data-Driven Testing

Publisher Resources

ISBN: 9781783982707

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Selenium Design Patterns and Best Practices

by Dima Kovalenko

Continuous Integration

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.