Behavior Driven UI Automation (Agile Testing Days 2017, Potsdam)

Behavior Driven
Web UI Automation
with Selenium and
Cucumber/SpecFlow
Agile Testing Days 2017, Potsdam
16th November, 2017
Gáspár Nagy
coach • trainer • bdd addict • creator of specflow
“The BDD Books: Discovery” • http://bddbooks.com
@gasparnagy • gaspar@specsolutions.eu

Copyright © Gaspar NagyCopyright © Gaspar Nagy
bdd addict
given.when.then
CAUTION!
on the stage
Gáspár Nagy
coach, trainer and bdd addict
creator of SpecFlow
gaspar@specsolutions.eu
https://specsolutions.eu
@gasparnagy

There are problems with UI test automation!
script
expressed using
UI terms
modeling gap
between UI terms and
domain model terms
sloooow
for a bigger app the
feedback loop gets
uselessly long
brittle
browsers changing,
environment changes,
cross-platform issues,
etc.

You are here*!
*hopefully

Unclear
purpose
Code
duplication
Anti-
semantic
locators
Wrong
abstraction
Timing
issues

Unclear purpose – What does it do?

Introduce BDD (SpecFlow/Cucumber)

Introduce Page Objects

Introduce Page Objects
Encapsulate interactions

Anti-semantic locators
• Think about how your users identify the different information (text, data,
controls, buttons, etc.) on the page
• If the user can find them, you will also find them… be smart!

Locating by ID is not enough!
[FindsBy(How = How.Id, Using = "cb9eb8be-71…")]
public IWebElement Khaki { get; set; }

Do not expose internals in the locators!
[FindsBy(How = How.Id, Using = "fabric_input")]
public IWebElement Fabric { get; set; }
fabric
fabric_input
fabric_list
fabric_open
@Html.Kendo().ComboBox().Name("fabric")
These are
internal for
the control!

Contextual semantics
[FindsBy(How = How.CssSelector, Using = "input.btn.btn-default")]
public IWebElement SubmitButton { get; set; }
The page may contain multiple forms later!

Define your own location strategy and
implement it as a custom locator!
[FindsBy(How = How.Custom,
CustomFinderType = typeof(TableFieldLocator)]
public IWebElement UserName { get; set; }
form
This is a
generic lookup
strategy
User Name
Password
input
input

public IWebElement UserName { get; set; }
Apply conventions with decorators and find the
tester’s nirvana…
form
This is the app-
specific lookup
strategy
User Name
Password
input
input

Wrong abstraction

Concept is an idea or mental picture of a group or
class of objects formed by combining all their aspects

UI Concepts
Counter concept,
divs and spans
Short-text entering
concept, input
@type=text
Multi-line text
entering concept,
div+javascriptSingle-choice concept,
set of input
@type=radio Submit concept,
span+javascript

A concept-based page
express concepts
interact on concept
level
For ConceptFactory implementation see:
https://github.com/gasparnagy/Sample_BehaviorDrivenWebUIAutomation

Thread.Sleep(3000);

Why do we have this timing problem?

An example
Enter text
Post form
Working, working…
Observe result
title.SendKeys(…);
button.Click();
driver.FindElement(…);

Let’s add some waiting to it!
Thread.Sleep(2000);
var wait = new WebDriverWait(driver, TimeSpan.FromSeconds(5));
wait.Until(d => d.FindElement(By...));
driver.Manage().Timeouts().ImplicitlyWait(TimeSpan.FromSeconds(5));
...
driver.FindElement(By...);
Static waiting
Busy/active waiting
Implicit busy waiting

An example
Enter text
Post form
Working, working…
Observe result
button.Click();
The thing you are waiting for is here!
You are waiting here!

Your user knows* when the action is done
*hopefully
• Maybe there is a progress indicator
• Maybe they look at the browser icon
• Maybe they’ll wait till they see the end of the page

An example
Enter text
Post form
Working, working…
Observe result
button.Click();
...wait for the footer
Result page loaded
button.SubmitClick()

Other conditions
• Wait until progress indicator is unloaded
• Wait until injected JavaScript signals that the operation has finished
• Wait until protractor signals
• You can even put Thread.Sleep there… only to that single place!
For all these, you need to isolate Submit/Click from other clicks

Thank you!
Gáspár Nagy
coach • trainer • bdd addict • creator of specflow
“The BDD Books: Discovery” • http://bddbooks.com
@gasparnagy • gaspar@specsolutions.eu

Behavior Driven UI Automation (Agile Testing Days 2017, Potsdam)

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (8)

Similar to Behavior Driven UI Automation (Agile Testing Days 2017, Potsdam)

Similar to Behavior Driven UI Automation (Agile Testing Days 2017, Potsdam) (20)

More from Gáspár Nagy

More from Gáspár Nagy (16)

Recently uploaded

Recently uploaded (20)

Behavior Driven UI Automation (Agile Testing Days 2017, Potsdam)