** WATCH FULL WEBINAR RECORDING HERE: https://youtu.be/06H-6hjyyvI ** What is Selenium? Why should you use it? And how do you use it successfully? In this webinar, Automation expert Dave Haeffner answers these questions as he steps through the why, how, and what of Selenium. Dave also discusses how to start from nothing and build out a well factored, maintainable, resilient, fast and scalable set of tests. These tests will not only work well, but across all of the browsers you care about, while exercising relevant functionality that matters to your business. Watch this webinar and learn how to: * Decompose an existing web application to identify what to test * Pick the best language for you and your team * Write maintainable and reusable Selenium tests that will be cross-browser compatible and performant * Dramatically improve your test coverage with automated visual testing * Build an integrated feedback loop to automate test runs and find issues fast

1. How To Use Selenium,
Successfully
by Dave Haeffner, @TourDeDave

2. http://www.wpclipart.com/geography/features/chasm.png.html

3. http://en.wikipedia.org/wiki/Optimal_solutions_for_Rubik's_Cube

4. Write business valuable tests that are
reusable, maintainable and resilient
across all relevant browsers.
Then package and scale them for
you & your team.

5. Selenium Overview
• What it is — the Reader’s Digest version
• What it is and is not good at
• IDE vs. Local vs. Remote
• Slow, brittle, and hard to maintain?

6. Step 1
Define a Test Strategy

7. Test Strategy
1. How does your business make money?
2. What features of your application are being used?
3. What browsers are your users using?
4. What things have broken in the app before?
Outcome:
- What features to test
- Which browsers to care about

8. Step 2
Pick a Programming
Language

9. Programming Language
• Same language as the app?
• Who will own it?
• Build a framework or use an existing one?
• http://se.tips/seleniumframeworks

10. Step 3
Use Selenium
fundamentals

11. Selenium Fundamentals
• Mimics human action
• Uses a few common actions
• Works with “locators”
Locators tell Selenium which HTML element to interact with

12. Common Actions
• get();
• findElement();
• click(); //or submit();
• sendKeys();
• isDisplayed();

13. Locator Strategies
• Class
• CSS selectors
• ID
• Link Text
• Partial Link Text
• Tag Name
• XPath
Good locators are:
• unique
• descriptive
• unlikely to change
That rules a few of these out

14. Locator Strategies
• Class
• CSS selectors
• ID
• Link Text
• Partial Link Text
• Tag Name
• XPath
Good locators are:
• unique
• descriptive
• unlikely to change
That rules a few of these out

15. Locator Strategies
• Class
• CSS selectors
• ID
• Link Text
• Partial Link Text
• Tag Name
• XPath
Good locators are:
• unique
• descriptive
• unlikely to change
That rules a few of these out
Start with IDs and Classes

16. Locator Strategies
• Class
• CSS selectors
• ID
• Link Text
• Partial Link Text
• Tag Name
• XPath
Good locators are:
• unique
• descriptive
• unlikely to change
That rules a few of these out
Start with IDs and Classes
Use CSS or XPath (with care)

17. Locator Strategies
• Class
• CSS selectors
• ID
• Link Text
• Partial Link Text
• Tag Name
• XPath
CSS vs XPath
http://se.tips/seleniumbenchmarks
http://se.tips/cssxpathexamples

18. Finding Quality Locators
• Inspect the page
• Verify your selection
• e.g., FirePath or FireFinder
• http://se.tips/verifyinglocators
• e.g., JavaScript console with $$(‘’); or $(‘’);
• Learn through gaming
• http://se.tips/locatorgame
• Conversation

20. Step 4
Write your first test

21. Good Test Anatomy
• Write for BDD or xUnit test framework
• Test one thing (atomic)
• Each test can be run independently (autonomous)
• Anyone can understand what it is doing
• Group similar tests together

22. A Login Example
1. Visit the login form
2. Find the login form’s username field and input text
3. Find the login form’s password field and input text
4. Find the submit button and click it
1. or, find the form and submit it

23. http://the-internet.herokuapp.com/login

26. Now to find an assertion
1. Login
2. Inspect the page
3. Find a locator
4. Verify it
5. Add it to the test

29. A much better assertion

30. Automated Visual Testing Primer
• Check that an application’s UI appears correctly
• Can also be used to verify content
• Hundreds of assertions for a few lines of code
• Open-source libraries, baseline image comparison,
and inherent challenges
http://se.tips/visual-testing-getting-started

31. In pom.xml

38. Exception Handling
• org.openqa.selenium.NoSuchElementException:
Unable to locate element: {"method":"css
selector","selector":".flash.error"}
• Most common ones you’ll run into:
NoSuchElement and
StaleElementReferenceError
• A list of all WebDriver exceptions:
http://se.tips/se-exceptions-java

39. Exception Handling cont’d
http://se.tips/se-exceptions-howto

40. Step 5
Write reusable and
maintainable test code

41. Page Objects

42. Application Under Test
Test 1 Test 2 Test 3 Test 4 Test 5Test 1 Test 2 Test 3 Test 4 Test 5
Need to update EVERY test :-(

43. Page Object(s)
Application Under Test
Test 1 Test 2 Test 3 Test 4 Test 5
Need to update JUST the page object :-D

44. Let’s look at a page
object for login

46. And here’s what the test
looks like when using it

47. Page object helpers:
http://se.tips/po-html-elements
http://se.tips/po-page-factory

48. Base Page Object
a.k.a.
Selenium Wrapper
Utility Class
etc.

49. Selenium
Commands
Page
Object 1
Page
Object 2
Page
Object 3
Page
Object 4
Page
Object 5

50. Base Page
Object
Page
Object 1
Page
Object 2
Page
Object 3
Page
Object 4
Page
Object 5
Selenium
Commands
• Global reuse
• More readable
• Insulates you from
Selenium API changes
http://se.tips/se-upgrade

51. Let’s take a look at a
Base Page Object

53. And here it is
implemented

55. How everything fits together
Test TestTest
Page
Object
Page
Object
Base
Page
Object
Tests use page objects
Page objects inherit the
base page (utility) class
The base page object wraps
your Selenium commands

56. Step 6
Make your tests resilient

57. Waiting

58. Thread.sleep();
Implicit wait
Explicit waits

59. Thread.sleep();
Implicit wait
Explicit waits

60. Thread.sleep();
Implicit wait
Explicit waits
http://se.tips/se-waiting

61. Explicit Waits
• Specify an amount of time, and an action
• Selenium will try repeatedly until either:
• The action is completed, or
• The amount of time specified has been reached
(and throw a timeout exception)

63. In the Base page object

64. In the DynamicLoading page object

65. Browser Timing
Considerations

66. Step 7
Prep for use

67. Test Harness
• Simple organizational structure
• Central setup and teardown
• Configurable at run-time (with sensible defaults)
• Reporting & Logging
• Parallelization
• Test Grouping

68. Folder structure

69. Central setup/teardown
More on JUnit Rules:
http://bit.ly/junit-rules

70. Simple config with defaults
Import config where it’s needed
(e.g., base test, etc.)

71. Reporting & Logging
• Machine readable
e.g., JUnit XML
• Human readable
e.g., screenshots, failure message, stack trace
Fantastic Test Report Tool
http://bit.ly/se-reporter (Allure Framework)

72. Parallelization
• In code
• Through your test runner
• Through your Continuous Integration (CI) server
#protip Enforce random order execution of tests
(turnkey in mvn-surefire)
Recommended approach:
http://bit.ly/mvn-surefire

73. Test Grouping
• Metadata (a.k.a. Categories)
• Enables “test packs”
• Some category ideas
• defect
• shallow & deep
• release or story number
More info:
bit.ly/junit-categories

74. Step 8
Add in cross-browser
execution

75. Locally
http://se.tips/se-chromedriver
http://se.tips/se-firefoxdriver
http://se.tips/se-iedriver
http://bit.ly/edge-driver
http://se.tips/se-safaridriver

76. Chrome

77. Grid
Grid Hub
Browser
Tests
All done with the Selenium Standalone Server
Just requires additional runtime flags
Grid
Node
Grid
Node
Grid
Node
Browser
Browser

78. Grid
Hub
Node(s)

79. Grid
• http://se.tips/grid-getting-started
• http://se.tips/se-grid-extras
• http://se.tips/se-grid-scaler

80. Sauce Labs
Sauce Labs Browser
Tests
http://se.tips/sauce-getting-started
http://se.tips/sauce-with-applitools

81. Step 9
Build an automated
feedback loop

82. Feedback loops
• The goal: Find failures early and often
• Done with continuous integration and notifications
• Notifications
- remote: Email, chat, SMS
- in-person: audio/visual indicators

83. Code
Committed
Unit/Integ.
(pass?)
Deploy to
autom. test
server
(success?)
Run
automated
tests
(pass?)
Deploy to
next env.
yes
yes
yes
Notify team if no
Code Promotion
Bonus points: stop the line

84. Simple CI configuration
1. Create a Job
2. Pull In Your Test Code
3. Set up Build Triggers
4. Configure Build steps
5. Configure Test Reports
6. Set up Notifications
7. Run Tests & View The Results
8. High-five your neighbor

86. Step 10
Find information on
your own
http://se.tips/selenium-resources

87. Steps to solve the puzzle
1. Define a Test Strategy
2. Pick a programming language
3. Use Selenium Fundamentals
4. Write Your First Test
5. Write re-usable and maintainable
test code
6. Make your tests resilient
7. Package your tests into a framework
8. Add in cross-browser execution
9. Build an automated feedback loop
10. Find information on your own

88. Write business valuable tests that are
reusable, maintainable and resilient
across all relevant browsers.
Then package them and scale them
for you & your team.

89. –Dave Haeffner
“You may think your puzzle is unique. But really, everyone is
trying to solve the same puzzle. Yours is just configured
differently — and it’s solvable”

90. 1. Sign up for a free Applitools Eyes account
http://se.tips/applitools-free-account
2. Run your first visual test
3. Email webinars@applitools.com
4. Sport your new “Visually Perfect” Tee
FREE t-shirt give-away
FREE sample of my book
• First 6 chapters available at
https://seleniumguidebook.com/#sample
• Available in Java and Ruby
• JavaScript, C#, and Python coming SOON!