Selenium WebDriver 3x (Java)

SQA-017
Functional UI Testing
with Selenium Web Driver
3.0
www.luxoft-training.pro
Introduction
• Let’s introduce ourselves
• Name & Position - Marian Constantin, Team Lead Luxoft
• Automation Testing experience
• Selenium experience
• What are your expectations from this course?

• Administrative?
• Schedule: TBD
• Breaks: every hour / on request
• Questions & Recap every chapter

Prerequisites
• Basic Testing Automation principles
• Programming Principles
• OOP
• Java (or similar language) 🡪 Hello World level ☺
• Nice to have
• JavaScript, jQuery
• HTML
• CSS
• XPath
Agenda
• Introduction to Selenium
• WebDriver
• WebElement
• Locators
• Waits
• Design Patterns
• Advanced Selenium
• Grid
Resources
• IntelliJ IDEA (Community Edition)
• Maven (bundled with IDEA)
• Git
• Firefox & Chrome, Developer Tools

• Junit, TestNG
• https://github.com/constanm/qa-upskilling
Environment Setup
SELENIUM ECOSYSTEM
What is Selenium?
• Selenium controls web browsers
• a toolset for web browser automation to remotely control browser instances
• emulates a user’s interaction with the browser
• One interface to rule them all

• guiding principle: support a common interface for all (major) browser technologies.
• tests can be run on different browsers and multiple operating systems across a
range of machines
• Tools and support
• can be included as a component in bigger applications
• gives you the tools to put together your grid of browsers
Terminology I
• API
• This is the set of commands you use to manipulate WebDriver.
• https://www.selenium.dev/selenium/docs/api/java/index.html
• Library
• A code module which contains the APIs and the code necessary to
implement them.
• Libraries are specific to each language binding, eg .jar files for Java, .dll files
for .NET, etc.
Selenium WebDriver - language bindings && implementations of the individual browser controlling
code
Terminology II
• Driver
• Responsible for controlling the actual browser
• Usually created by the browser vendors themselves
• Executable modules that run on the system with the browser itself, not on the
system executing the test suite
• Framework
• An additional library used as a support for WebDriver suites
• May be test frameworks (JUnit, NUnit, pytest), even supporting natural language
features (Cucumber, Robotium)
• May be written and used for manipulating or configuring the SUT, data creation, test
oracles, etc.
SELENIUM: ECOSYSTEM
• Selenium WebDriver
• drives a browser natively, as a user would, either locally or on a
remote machine using the Selenium server
• Accepts commands using Client API and send them to browser
launched by driver class
• Listen commands from Selenium API → converts commands to
browser native API → send native commands output back
• Collection of language-specific client libs
https://selenium.dev/documentation/en/
SELENIUM: ECOSYSTEM
• Selenium Server
• Allows test run on remote machine browser instances
• Allows parallel run → load balancing
• Selenium Grid → node-hub topology
SELENIUM: ECOSYSTEM
• Selenium IDE (not supported)
• Record-playback Firefox add-on
• Quick and simple scripts
• Automation-aided exploratory testing
• Macros for repetitive web-pages tasks
SELENIUM: WebDriver - direct communication
SELENIUM: Remote WebDriver
SELENIUM: Selenium Server/Grid
SELENIUM: Framework
SELENIUM: 2.0 → 3.0
•Necessary bug fixes

•The Selenium Core is obsolete
•Java 8+
•Changes made in W3C webdriver specification
•Selenium Grid Stability fixes
SELENIUM WEBDRIVER
SELENIUM: W3C
• Selenium WebDriver is a W3C Recommendation

● WebDriver is designed as a simple and more concise programming
interface
● WebDriver is a compact object-oriented API
● It drives the browser effectively
https://www.w3.org/TR/webdriver1/
WEBDRIVER: W3C SPEC
• Protocol
• Remote end – HTTP server
• Commands – HTTP Requests with appropriate sequence of actions on

the remote end
• Each command produces single HTTP response
• Session – one instance of browser
WEBDRIVER: W3C SPEC
• Nodes
• Local end – client side implementation for WebDriver protocol in form
of language-specific libraries (Java, C#, Ruby etc...)
• Remote end – defines behaviour in response of WebDriver commands

at endpoint nodes (user agents) (WebDriver implementations –
Chrome, IE, Safari,Firefox etc...)
WEBDRIVER: Selenium WebDriver
• Drives a browser natively, as a user would, either locally or on a
remote machine using the Selenium server
• Accepts commands using Client API and send them to browser
launched by driver class
• Listen commands from Selenium API → converts commands to
browser native API → send native commands output back
• Collection of language-specific client libs
https://selenium.dev/documentation/en/
WEBDRIVER: Requirements
• Aim - to emulate a real user’s interaction with the browser as

closely as possible
• Supports all major browsers on the market:
• Chrome(ium), Firefox, Internet Explorer, Edge, Opera, Safari
• Driver implementations are provided by third parties
• Instantiation, profile management, various browser specific settings
• Most drivers require an extra executable
• manually provided path
• setx /m path "%path%;C:\path\to\webdriver\binaries\"
WEBDRIVER: W3C SPEC- sample endpoints
• https://www.w3.org/TR/webdriver1/#list-of-endpoints
WEBDRIVER: W3C SPEC - errors
WEBDRIVER IMPLEMENTATIONS
WD IMPLEMENTATIONS: FIREFOX DRIVER
• https://github.com/mozilla/geckodriver
• webdriver.gecko.driver property
• FirefoxOptions fo = new FirefoxOptions()
• fo.setHeadlessMode(boolean) – CI
• fo.setProfile(fp)
• FirefoxProfile fp = new FirefoxProfile
• fp.addExtension(File extensionXpiFile)
• fp.setPreferences(String key, String value)
SELENIUM: FIREFOX DRIVER
Examples:
FirefoxProfile profile = new FirefoxProfile();
profile.addExtension( new
File("./src/test/resources/extensions/xpath_finder.xpi"));
FirefoxOptions firefoxOptions = new FirefoxOptions();
firefoxOptions.setHeadless(true);
firefoxOptions.setProfile(profile);
driver = new FirefoxDriver(firefoxOptions);
WD IMPLEMENTATIONS: CHROME DRIVER
• http://chromedriver.chromium.org/
• webdriver.chrome.driver property
• ChromeOptions co = new ChromeOptions()
• co.setHeadlessMode(boolean)
• co.addExtension(File extensionCrxFile)
SELENIUM: CHROME DRIVER
Examples:
ChromeOptions chromeOptions = new ChromeOptions();
chromeOptions.addExtensions(new File("/path/to/extension.crx"));
chromeOptions.setHeadless(true);
driver = new ChromeDriver(chromeOptions);
WD IMPLEMENTATIONS: CHROME MOBILE EMULATION
• setExperimentalOption("mobileEmulation",
HashMap<String, Object> me)
• deviceMetrics – screen parameters – via HashMap
• userAgent – mobile device used during testing – via String
SELENIUM: EXPERIMENTAL MODE
Examples:
Map<String, Object> deviceMetrics = new HashMap<>();
deviceMetrics.put("width", 430);
deviceMetrics.put("height", 853);
deviceMetrics.put("pixelRatio", 2.0);
Map<String, Object> mobileEmulation = new HashMap<>();
mobileEmulation.put("deviceMetrics", deviceMetrics);
mobileEmulation.put("userAgent", "Mozilla/5.0 (Linux; Android 8.0.0;"
+ "Pixel 2 XL Build/OPD1.170816.004) AppleWebKit/537.36
(KHTML, like Gecko) "+"Chrome/67.0.3396.99 Mobile Safari/537.36");
chromeOptions.setExperimentalOption("mobileEmulation",
mobileEmulation);
driver = new ChromeDriver(chromeOptions);
WD IMPLEMENTATIONS: OTHERS
• https://github.com/SeleniumHQ/selenium/wiki/InternetExplorerDriver
• https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver
• Safari built-in
WD FEATURES: NAVIGATION
• Navigation
• get("https://selenium.dev")
• back()
• forward()
• refresh()
WD FEATURES: TAKING SCREENSHOTS
Examples:
driver = new ChromeDriver();
driver.get("http://www.google.com");
File scrFile =
((TakesScreenshot)driver).getScreenshotAs(OutputType.FILE);
FileUtils.copyFile(scrFile, new
File("./target/googleShot.png"));
WD FEATURES: SWITCHING TABS
• String webDriver.getWindowHandle() – current tab
• Save to switch back
• Set<String> webDriver.getWindowHandles() – all tabs
• webDriver.switchTo().window(String) – switch
WD FEATURES: Tabs, Windows, Frames
Examples:
String firstTab = driver.getWindowHandle();
System.out.println("First tab is: " + firstTab);
WebElement button = driver.findElement(By.tagName("button"));
button.click();
String secondTab = driver.getWindowHandle();
System.out.println("Second tab is: " + secondTab);
System.out.println("Number of tabs "+
driver.getWindowHandles().size());
driver.switchTo().window(firstTab);
WD FEATURES: ALERTS
• module-selenium.webdriver.common.alert
• accept() = OK
• dismiss() = Cancel
• text()
• sendKeys()
• driver.switchTo().alert();
SELENIUM: PROMPTS
Examples:
# Wait for the alert to be displayed

wait.until(ExpectedConditions.alertIsPresent())
# Store the alert in a variable for reuse

Alert alert = driver.switchTo().alert();
# Type your message

alert.sendKeys("Selenium")
WD FEATURES: JAVASCRIPT CODE EXECUTION
Common usages
• get elements text or attribute
• find an element
• do some operation on an element, like click()
• change attributes of an element
• scroll to an element or location on a web page
• wait until the page is loaded
WD FEATURES: JAVASCRIPT CODE EXECUTION
• Synchronously Executes JavaScript in the current window/frame.

• executeScript
• Asynchronously Executes JavaScript in the current window/frame.
• executeAsyncScript
SELENIUM: JAVASCRIPT
Examples:
WebDriver driver = new ChromeDriver();
JavascriptExecutor js = (JavascriptExecutor) driver;
String title = (String) js.executeScript("return
document.title");
assertEquals("Google", title);
WD FEATURES: COOKIES
• For example to skip sign in actions
• webDriver.manage().
• Set<Cookie> getCookies()
• Cookie getCookieNamed(String)
• addCookie(Cookie)
• deleteCookie(Cookie)
• deleteAllCookies()
SELENIUM: COOKIES
Examples:
WebDriver wd = new FirefoxDriver();
Cookie cookie = new
Cookie("SeleniumIntroductionCookie","SICookieValue");
wd.manage().addCookie(cookie);
System.out.println(wd.manage().getCookieNamed("SeleniumIntroductionCoo
kie"));
wd.manage().deleteCookie(cookie);
MatcherAssert.assertThat(
wd.manage().getCookieNamed("SeleniumIntroductionCookie"),
is(nullValue()));
WEB ELEMENT
SELENIUM: WEBELEMENTS
• Common elements
• links
• textboxes
• buttons
• radio buttons
• checkboxes
• body
• labels
• With Selenium we are locating elements and manipulating them
SELENIUM: ELEMENTS INSPECTION
• Document Object Model tree
• Firefox/Chrome have Inspect Element right-click on element menu

item
• Generate XPath/CSS selectors for further processing
• $("css_selector") or $x("xpath_selector")
SELENIUM: findElement(s)
• By instance as argument – locating mechanism
• findElement
• Return WebElement instance representing actual HTML element
• First element satisfying By criteria
• NoSuchElementException (runtime) found no elements
• findElements
• Return list of WebElements
• Empty list when no elements found
SELENIUM: findElement(s)
Syntax:
public WebElement findElement(By locator)
public List<WebElement> findElements(By locator)
SELENIUM: BY - locator strategies
Selenium gives user options to locate elements in 8 different ways.

1. Id
2. Name
3. Linktext
4. Partial Linktext
5. Tag Name
6. Class Name
7. CSS (Cascaded Style Sheets)
8. XPath (XML path)
SELENIUM: Find element and interact example
driver.findElement(By.id("search_query_top")).sendKeys("dress");
driver.findElement(By.partialLinkText("Contact")).click();
driver.findElements(By.xpath("//input[@name='id_gender']"))
.get(1).click();
SELENIUM: BY - XPath
Syntax:
By.xpath xpathSelector
Examples:
"/html/body/div/div/form/input" – absolute path
"//input" – relative path
"//input[2]" – specific element
"//input[@type='submit'][@value='Login']" - attribute
"//input[contains(@id,'userName')]" – attribute value
"//*[@class='price']" – when node type is unknown
"//td[contains(text(),'Item 1')]" – by element text
SELENIUM: BY - CSS
Syntax:
By.cssSelector cssSelector
Examples:
"html > body > div > div > form" – parent-to-child
"input#username" – using id
"input.login" – using class
"input[type='submit']" - attribute
"input[id*='userName']" – attribute value substring
ELEMENTS: PROPERTIES & ATTRIBUTES
• String getAttribute()
• name, id, class, value…
• String getText()
• String getCssValue(String )
• height, width, padding…
• If assigned to class in CSS
ELEMENTS: PROPERTIES & ATTRIBUTES
• Point getLocation()
• Relative element position after page rendering
• Top-left corner – (0,0)
• Dimension getSize()
• Width & height
• String getTagName()
SELENIUM: PROPERTIES & ATTRIBUTES
Examples:
WebElement loginButton =
webDriver.findElement(By.id("login"));
String btnAlign = loginButton.getAttribute("align");
Assertions.assertTrue(loginButton.getText().contains("Login");
String btnWidth = loginButton.getCssValue("width");
Point btnLocation = loginButton.getLocation();
Dimension btnSize = loginButton.getSize();
Assertions.assertEquals("button",loginButton.getTagName());
ELEMENTS: ACTIONS
• sendKeys(CharSequence)
• Keys enum – Enter, Ctrl, Esc
• Keys.chord(Keys.SHIFT, "text")->TEXT
• clear()
• submit()
• When inside "form" element, if not – NoSuchElementException
ELEMENTS: STATE
• isDisplayed()
• isEnabled()
• isSelected()
• Radiobutton, select list options, checkbox
SELENIUM: STATE & ACTIONS
Examples:
WebElement checkBox = driver.findElement(By.name("option_box"));
if (checkBox.isEnabled()) {
if (!checkBox.isSelected()) {
checkBox.click();
}
} else {
fail("Option Checkbox is disabled!!");
}
ELEMENTS: SELECT
• Dropdown list wrapper
• new Select(driver.findElement(By.name("make")))
• selectByVisibleText(String)
• (de)selectByValue(String)
• (de)selectByIndex(int)
• List<String> getOptions()
• boolean isMultiple()
SELENIUM: SELECT
Examples:
Select shopLocation = new
Select(driver.findElement(By.className("shop_location")));
boolean isMultiple = shopLocation.isMultiple()
if (isMultiple) {
int listSize = shopLocation.getOptions().size();
}
shopLocation.selectByVisibleText("Poland");
shopLocation.selectByValue("Belarus");
shopLocation.selectByIndex(4);
//if multiple
int selectedLocations = shopLocation.getAllSelectedOptions().size()
WEBDRIVER WAITS
WD WAITS: syn vs. asyn
• The normal instruction set available on the WebElement interface

are guaranteed to be synchronous ( element.click,
element.sendKeys)
• the function calls will not return until the command has been
completed in the browser.
• The advanced user interaction APIs, Keyboard and Mouse, are
exceptions as they are explicitly intended as “do what I say”
asynchronous commands.
WD WAITS: IMPLICIT WAIT
• WebDriver polls the DOM for a certain duration when trying to find
any element.
• The default setting is 0, meaning disabled.
• Once set, the implicit wait is set for the life of the session.
WD WAITS: IMPLICIT WAIT
• Warning: Do not mix implicit and explicit waits!

• Doing so can cause unpredictable wait times. For example, setting
an implicit wait of 10 seconds and an explicit wait of 15 seconds
could cause a timeout to occur after 20 seconds.
• An implicit wait is to tell WebDriver to poll the DOM for a certain
amount of time when trying to find an element or elements if they
are not immediately available.
Implicit wait example
Examples:

wd.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);
WD WAITS: EXPLICIT WAIT
• Allow your code to halt program execution, or freeze the thread,

until the condition you pass it resolves.
• The condition is called with a certain frequency until the timeout of
the wait is elapsed.
• This means that for as long as the condition returns a falsy value, it
will keep trying and waiting.
Expected Conditions
Common checks are already defined as ExpectedConditions
Examples:
• alert is present
• element exists
• element is visible
• title contains
• title is
• element staleness
• visible text, etc.
SELENIUM: EXPLICIT WAIT
Examples:
WebElement WebDriverWait(wd, 10).until(
ExpectedCondition<WebElement>d->d.findElement(By.id("search"))
)

WebElement WebDriverWait(wd, 30).until(
ExpectedConditions.presenceOfElementLocated(By.tagName("a"))
)
WD FEATURES: FLUENT WAIT
• Custom pooling time and exception ignoring capability
new FluentWait<WebDriver>(driver)
.withTimeout(int, TimeUnit)
.pollingEvery(int, TimeUnit)
.withMessage(String)
.ignoring(Throwable, Throwable)
SELENIUM: FLUENT WAIT
Examples:
public static WebElement findElementWithFluentWait(WebDriver wd, By
locator) {
return new FluentWait<>(wd)
.withTimeout(Duration.ofSeconds(60))
.pollingEvery(Duration.ofSeconds(1))
.ignoring(StaleElementReferenceException.class,
NoSuchElementException.class)
.until(webDriver -> webDriver.findElement(locator));
}
WEBDRIVER ADVANCED ELEMENT
INTERACTIONS
ADVANCED INTERACTIONS: ACTION CHAINS
• Mouse-based & keyword-based actions
• Actions class to create complex user events
• Action class to call perform()
ADVANCED INTERACTIONS : 3 STEPS
The action creation process:
1. Create Actions object (builder)

2. Build complex action by chaining the simple one (call build()
when end)
3. On build() result Action instance call perform()
ADVANCED INTERACTIONS : MOUSE-BASED
• Actions moveByOffset(int xOffset, int yOffset)
• Mouse in (0,0) by default after page load
• Move mouse pointer from current to the specified by offset position
• MoveTargetOutOfBounds exception when move out of document

• Actions click()/click(WebElement onElement)
• Left-button click on current mouse position/on target
• Actions clickAndHold()/ clickAndHold(WebElement
onElement) – for drag-and-drop
• Actions release()/ release(WebElement onElement) –

release mouse button
• Actions contextClick()/(WebElement onElement) –

right-button mouse
• Actions moveToElement(WebElement onElement)
• Actions dragAndDropBy(WebElement source, int

xOffset, int yOffset)
• Actions dragAndDrop(WebElement souce, WebElement

target)
• Actions doubleClick()/doubleClick(WebElement
onElement)
• Actions dragAndDropBy(WebElement source, int
xOffset, int yOffset)
• Actions dragAndDrop(WebElement souce, WebElement

target)
• Actions doubleClick() – current position
• Actions doubleClick(WebElement onElement)
ADVANCED INTERACTIONS : KEYBOARD-BASED
• Actions keyDown(Keys key) - press and hold the key
• Shift, Ctrl, Alt; other – IllegalArgumentException
• Actions keyUp(Keys key) – release the key
• without keyDown() - ???
• Actions sendKeys(CharSequence)
SELENIUM: ACTIONS
Examples:
WebDriver wd = new ChromeDriver();
Actions builder = new Actions(wd);
Action complexMove =
builder.moveToElement(wd.findElement(By.id("id1")))
.pause(Duration.ofSeconds(2))
.moveToElement(wd.findElement(By.id("id2")))
.click()
.build();
complexMove.perform();
DESIGN PATTERNS
COMMON DESIGN PATTERNS
● Domain Driven Design: Express your tests in the language of the end-user of
the app.
● PageObjects: A simple abstraction of the UI of your web app.
● LoadableComponent: Modeling PageObjects as components.
● BotStyleTests: Using a command-based approach to automating tests, rather
than the object-based approach that PageObjects encourage
● AcceptanceTests: Use coarse-grained UI tests to help structure development
work.
● RegressionTests: Collect the actions of multiple AcceptanceTests into one
place for ease of maintenance. … read more on Design-Patterns
PAGE OBJECT: MARTIN FOWLER
• https://martinfowler.com/bliki/PageObject.html
• HTML page wrapper with an application-specific API
• Hide details of UI structure from test
• Should allow anything that a human can do ← rule of
• Use inheritance
• Limited or no assertions
• Case study:
• https://github.com/SeleniumHQ/selenium/wiki/PageObjects
PAGE OBJECT
• A page object is an object-oriented class that serves as an

interface to a page of your AUT.
• Used for enhancing test maintenance and reducing code
duplication
• Main benefit:
• if the UI changes for the page, the tests themselves don’t need to
change, only the code within the page object needs to change.
Advantages of Page Object
● There is a clean separation between test code and page specific
code such as locators (or their use if you’re using a UI Map) and
layout.
● There is a single repository for the services or operations offered by
the page rather than having these services scattered throughout
the tests.
SELENIUM GRID
Selenium Grid
• A smart proxy server that allows tests to route commands to remote
web browser instances.
• Its aim is to provide an easy way to run tests in parallel
• on multiple machines
• with different browser versions
• different browser configurations
• One server acts as the hub that routes JSON formatted test
commands to one or more registered Grid nodes.
• Tests contact the hub to obtain access to remote browser
instances.
•
Purposes and main functionalities
● Central entry point for all tests
● Management and control of the nodes / environment where the
browsers run
● Scaling
● Running tests in parallel
● Cross platform testing
● Load balancing
Components of a Grid
SELENIUM GRID: SELENIUM SERVER
• Download JAR to the remote machine where browsers located
• Start the server:
java -jar selenium-server-standalone-{VERSION}.jar
• Timeout mode:
java -jar selenium-server-standalone-{VERSION}.jar
-timeout=20 -browserTimeout=60
SELENIUM GRID: Remote WebDriver
• Can be used similar to a local WebDriver

• a remote WebDriver needs to be configured so that it can run your
tests on a separate machine
• once configured, it needs to be started and can be referenced
• A remote WebDriver is composed of two pieces:
• a client - your WebDriver test
• a server - a Java servlet, which can be hosted in any modern JEE
app server
SELENIUM GRID: SCRIPT CHANGES
• Instantiate a Remote WebDriver and pass any Options or

DesiredCapabilities supported
• Server console will reflect all established sessions
• 4444 – default port, use –port parameter to set up custom port
Remote for Chrome
chromeOptions.setCapability("browserVersion", "67");
chromeOptions.setCapability("platformName", "Windows XP");
WebDriver driver = new RemoteWebDriver(new
URL("http://www.example.com"), chromeOptions);
driver.quit();
Remote for Firefox
FirefoxOptions firefoxOptions = new FirefoxOptions();
WebDriver driver = new RemoteWebDriver(new
URL("http://www.example.com"), firefoxOptions);
driver.quit();
Upload files on Remote
// set up local file detector
driver.setFileDetector(new LocalFileDetector());
// do the upload
driver.get("http://sso.dev.saucelabs.com/test/guinea-file-upload"
);
WebElement upload = driver.findElement(By.id("myfile"));
upload.sendKeys("/Users/sso/the/local/path/to/darkbulb.jpg");
SELENIUM GRID: accessing the Grid web interface
• Web interface
SELENIUM GRID: HUB
• Intermediary and manager

• Accepts requests to run tests
• Takes instructions from client and executes them remotely on the nodes
• Manages threads
• -role hub parameter
• See console output for node configuration info
java -jar selenium-server-standalone.jar -role hub
java -jar selenium-server-standalone.jar -role hub

-hubConfig hubConfig.json -debug
SELENIUM GRID: STEPS PERFORMED
• Hub:
• Get request to create new session with requested options
• If available – create session, if not – rejects
• Create new test-slot session and redirect script to the node
• Registering a Node:
java -jar selenium-server-standalone.jar -role node -hub
http://localhost:4444
SELENIUM GRID: NODE
• Node
• Where the browsers live
• Registers itself to the hub and communicates its capabilities
• Receives requests from the hub and executes them
• Registering a Node:
java -jar selenium-server-standalone.jar -role node -hub
http://localhost:4444
SELENIUM GRID: STEPS PERFORMED
• Node:
• Creates new session with desired options
• Executes test scripts in browser
• Forwards result to the hub
SELENIUM GRID: CONFIGURATION
• Set node supported browsers
• -browser browserName=firefox -browser browserName=chrome
• Node timeout (seconds) – hub waits before script execution

termination
• -nodeTimeout 300
• Limit of node browser instances

• -browser "browserName=chrome,maxInstances=3"
SELENIUM GRID: CONFIGURATION
• Set hub new session timeout
• -newSessionWaitTimeout 120000
• Wait for desired capability node (not reject request)

• -throwOnCapabilityNotPresent false
GUIDELINES
The DOs..
• Page Object models
• Domain specific language
• Generating application state
• Mock external services
• CI and Improved reporting
• Avoid sharing state
• Test independency
• Consider using a fluent API
• Fresh browser per test
Domain specific language (DSL)
• Readable: Business stakeholders can understand it.
• Writable: Easy to write, avoids unnecessary duplication.
• Extensible: Functionality can (reasonably) be added without
breaking contracts and existing functionality.
• Maintainable: By leaving the implementation details out of test
cases, you are well-insulated against changes to the AUT.
Generating application state
• Selenium should not be used to prepare a test case.
• All repetitive actions and preparations for a test case, should be
done through other methods.
• Eliminating logging in via web browser before every test will
improve both the speed and stability of the test.
• A method should be created to gain access to the AUT*
• e.g. using an API to login and set a cookie.
• Input data should not be created by Selenium
www.luxoft-training.pro •
Avoid sharing state
• Do not share test data.
• Imagine several tests that each query the database for valid orders
before picking one to perform an action on. Should two tests pick
up the same order you are likely to get unexpected behaviour.
• Clean up stale data in the application that might be picked up by
another test
• e.g. invalid order records.
• Create a new WebDriver instance per test.
• This helps ensure test isolation and makes parallelization simpler.
Domain specific language
• Mock external services
• greatly improve the speed and stability of your tests
• CI and Improved reporting
• Test independency
• a test shouldn’t depend of affect another test.
• Consider using a Fluent API
• object-oriented API whose design relies extensively on method
chaining. Its goal is to increase code legibility by creating a DSL
• Fresh browser per test
.. and the DON’Ts!
• CAPTCHA - disable or bypass, don’t try to automate
• Although possible, don’t try to test file downloads
• Don’t try to verify HTTP response codes
• Automating logins for Facebook, Gmail, Tinder, etc. - No!
• Shouldn’t try to order test execution
• Performance testing → jmeter
• Web crawling
REFERENCES
• https://selenium.dev
• https://www.safaribooksonline.com/library/view/selenium-webdriver-3
/9781788999762/
• https://www.safaribooksonline.com/library/view/selenium-testing-tools
/9781784392512/

Selenium WebDriver 3x (Java)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Selenium WebDriver 3x (Java)

Uploaded by

Copyright:

Available Formats

SQA-017

• What are your expectations from this course?

• Breaks: every hour / on request

• Questions & Recap every chapter

• Maven (bundled with IDEA)

• Firefox & Chrome, Developer Tools

• One interface to rule them all

• Allows parallel run → load balancing

• Selenium Grid → node-hub topology

• Quick and simple scripts

• Automation-aided exploratory testing

• Macros for repetitive web-pages tasks

•Necessary bug fixes

• Selenium WebDriver is a W3C Recommendation

• Commands – HTTP Requests with appropriate sequence of actions on

• Each command produces single HTTP response

• Session – one instance of browser

• Remote end – defines behaviour in response of WebDriver commands

• Aim - to emulate a real user’s interaction with the browser as

• deviceMetrics – screen parameters – via HashMap

• userAgent – mobile device used during testing – via String

• Save to switch back

• Set<String> webDriver.getWindowHandles() – all tabs

# Wait for the alert to be displayed

# Store the alert in a variable for reuse

# Type your message

• Synchronously Executes JavaScript in the current window/frame.

• Firefox/Chrome have Inspect Element right-click on element menu

• Generate XPath/CSS selectors for further processing

public List<WebElement> findElements(By locator)

Selenium gives user options to locate elements in 8 different ways.

• If assigned to class in CSS

• Top-left corner – (0,0)

• When inside "form" element, if not – NoSuchElementException

• Radiobutton, select list options, checkbox

• The normal instruction set available on the WebElement interface

• Warning: Do not mix implicit and explicit waits!

WebDriver wd = new FirefoxDriver();

• Allow your code to halt program execution, or freeze the thread,

WebDriver wd = new FirefoxDriver();

• Actions class to create complex user events

• Action class to call perform()

1. Create Actions object (builder)

• Move mouse pointer from current to the specified by offset position

• MoveTargetOutOfBounds exception when move out of document

• Actions release()/ release(WebElement onElement) –

• Actions contextClick()/(WebElement onElement) –

• Actions dragAndDropBy(WebElement source, int

• Actions dragAndDrop(WebElement souce, WebElement

• Actions dragAndDrop(WebElement souce, WebElement

• Actions doubleClick() – current position

• Actions doubleClick(WebElement onElement)

• Actions keyUp(Keys key) – release the key

• without keyDown() - ???

• A page object is an object-oriented class that serves as an

• Can be used similar to a local WebDriver

• Instantiate a Remote WebDriver and pass any Options or

• Intermediary and manager

java -jar selenium-server-standalone.jar -role hub

• If available – create session, if not – rejects

• Create new test-slot session and redirect script to the node

• Executes test scripts in browser