1.
MAKING
CROSS-BROWSER
TESTS
B f

2.
Ask me about:
● Continuous deployment
● Scaling automation
● Life @ startups

3.
● WHY
● HOW
● PROBLEMS
● SOLUTIONS
● LESSONS LEARNED
A

4.
WHAT DO YOU WANT
TO GET OUT OF THIS
SESSION?

5.
WHY ?

6.
● Increase confidence your app works in all browsers
● Can easily test changes in browsers
● Save time from manually testing features

7.
HOW ?

8.
● Answer the following questions:
○ Which browsers will be supported?
○ What is the most important workflow to test?
○ How will the tests be run?

9.
Write automated
tests for a student
loan refinance
application
TASK:

10.
Don’t know how
application works in
other browsers
PROBLEM:

11.
Implement
automated
cross-browser
tests
SOLUTION:

12.
Step 1: Decide Supported Browsers

13.
Step 1: Decide Supported Browsers

14.
Step 2: Decide what to automate
● What is the most crucial
workflow to automate?

15.
Step 3: Decide how to run tests

16.
Step 3: Decide how to run tests

17.
Step 4: Write some tests

18.
IT SHOULD BE AS
EASY AS CHANGING
THE DRIVER, RIGHT?

19.
PAGE ELEMENTS
PROBLEM
# 1

20.
● Cannot interact with elements in the same way across
browsers
● Dropdowns, radio buttons and checkboxes are tricky

21.
Element is not clickable

22.
Alternate clicking methods

23.
TIMING ISSUES
PROBLEM
# 2

24.
● Need to wait for elements….
● Running tests locally vs running remotely

25.
No Such Element

26.
IMPLICIT WAITS
Wait for a set amount of time

27.
EXPLICIT WAITS
Wait for an event up until a certain amount of time

28.
DRIVER
CAPABILITIES
PROBLEM
# 3

29.
● Drivers are managed separately
● Native capabilities differ
● Same functionality isn’t always available

30.
FILE UPLOAD

31.
The Safari Driver is implemented in JS and
does not have the privileges necessary to
manipulate an <input type = “file”> element.
Therefore, the SafariDriver does not
support file uploads.

32.
RESOLUTION

33.
● Maximize browser window
● Set a specific resolution at run-time
● Scroll an element into view

34.
LESSONS
LEARNED

35.
START TESTING
EARLY

36.
MAKE YOUR TEST SCRIPTS
UNIVERSAL

37.
USE WAITS AS
NEEDED

38.
Run tests in CI
regularly

39.
QUESTIONS?
LinkedIn: meaghan-lewis
Twitter: @iammeaghanlewis
Email: meaghan@lever.co