High sierra part 1

High Sierra
Selenium-based Testing
Validation, Workflow, Zalenium, Azure
Part 1 of 3 Copyright © 2019 David Harrison
Part 1 – Validation, Zalenium

Context
01
02
03
04
We are predominantly testing
Assert-Assert-Assert is the basic mantra of Test Automation
Sometimes we simulate something
Maybe we want to generate special data…etc.
We are members of a project
Whether Waterfall or Agile, we are participants
We are developing business value
We construct & deliver something of value to the project
© 2019 David Harrison, dharrison_ch@yahoo.co.uk, https://www.dharrisonch.com/, https://www.slideshare.net/DavidHarrison20/

The Story
What will be covered in this presentation
Validation is KING.
This is the bedrock of what we do in
Test Automation, as in any testing
Validation
When we have a mid- to large-
volume of tests, using a scalable
execution platform is something to
be considered
Zalenium
01
03 04

The
Target
Application
This web site provides an elegant, and challenging, platform for Test Automation
approaches to be developed:
Site: http://automationpractice.com/index.php
Its key themes are:
• Account creation
• Login for account holders
• Shopping for items in a store
• Search for items in store
• Shopping Cart
• Check out
• Delivery information
• Logout
• Strip Page site
Target Application

The
Approach
The approach showcased in this series, has the following characteristics:
• Validation: Unit Tests C#-based (https://docs.microsoft.com/en-
us/dotnet/core/testing/)
• Selenium-based tests (https://www.seleniumhq.org/)
• Workflow: Specflow-based (https://specflow.org/)
• Zalenium: (http://opensource.zalando.com/zalenium/)
• Azure Cloud: (https://docs.microsoft.com/en-
us/azure/devops/pipelines/test/continuous-test-selenium?view=azure-devops)
Approach

• Shop product groups
• Shop tabs
• Shop items have overlay @ hover
• Shop items have “Quick view” link on
hover
• Items have offers/reductions

Key Points
What are the important aspects of the app? The application is built using Ajax so we need to be
very aware of “waiting” for elements.
Ajax
Validating items in the storefront involves dealing
with multiple pages and overlays/offers/reductions
etc.
Storefront
Some of the Footer elements (in principle) declare
the legal basis for using the shopping site. We need
to validate the legal text.
Legal
01
02
03
A key element of this site is the state of the
Shopping Cart. This we need to validate.
Shopping Cart
04
Validating the correctness of key business
workflows is crucial to the testing of this site.
Business Workflow
05

Validation
What do we validate? We validate that some key page elements exist.
Existence
We validate that some key items are visible when
they are expected to be.
Visibility
We validate that the strip page can be moved and
that certain elements become visible/(not visible).
Movement
01
02
03
Validate that the store items on the Main page
display the appropriate data.
Storefront
04
Validate that the page footer shows the appropriate
important links – and that they show the correct
data (legal text).
Page Footer
05

Key Points
• We use a test properties object to manage generic and test-specific propertie
s
• We use Log4Net as our logging infrastructure
• We use of certain frameworks such as “DotNetSelenium.Extras.WaitHelpers”
to provide element wait functionality
• The Page Objects are generated by Se34 (https://www.dharrisonch.com/)
• For certain “special” operations we will use Selenium WebDriver JavaScript
(because of app “features”)
• For this example we use C#/.Net but we could equally as well be using Java
• We use the Chrome browser

Generating Page Objects
• Metadata describing “pages” (validations,
operations etc)
• Se34 used to generate fully finished Page
Object Classes (C#/Java)
• App change -> update ->re-generate

Generating Page Properties
• Se34 used to generate Property files
(optional)
• App change -> update ->re-generate
• Dynamic (run-time) values can be dealt with
using an Oracle (“xx = ?”)

UT - Assembly Initialization
• Adding test properties
• Set up Log4Net

UT - Test Class Instantiation
• Set up test base class
• Set up the site form
• Initialise the validation bit mask
• Initialise browser
• Initialise the shop data
• Initialise the error bit mask

UT - Test Initialization
• This is executed per unit test!
• Are we executing local tests?
• Configure WebDriver
• Maximise the browser window
• Set the implicit wait interval
• Instantiate the MainPage
• Navigate to it
• Wait for it

Initialise UT-Specific Properties

UT - Test Cleanup
Quit the driver – we renew the driver for each test

UT - Validate Existence
• Check that this UT can
run (local, remote etc)
• Note fluent validation
statement
• Check if errors detected
• Just a selection of
possibilities

UT - Validate Visibility
• Check that this UT can
run (local, remote etc)
• Use base class methods
to check for visibility
• Use base class methods
to move to bottom of strip
page
possibilities

UT - Validate Movement
• Check visibilities of elements
when scrolling the page
• Using base class methods to
scroll strip page
• Using base class methods to
check for visibility
possibilities

UT - Validate Storefront (1)
• Validate items for each type of storefront
• Select Store Tab and use local test
method to do the heavy lifting
• Log & Assert
• Just a selection of possibilities

• Local method that performs Asserts
• Need to manage physical cursor because of
item overlay
• Loop over items in the configured shop
data
• Need to take care of item overlay (frame)
(move physical cursor by small amount)
• Build the image, and other XPath
expressions
• Configure a local wait object
• We cant configure the XPath expressions
for all the elements of an item, they depend
on whether the item has a reduction
(dynamic)

• Check the existence of the various
pieces of the displayed item data
• Make us of the test properties to
get data
• Move physical cursor if the item
data suggests a reduction (remove
overlay)
• Validate Price/Old Price/Reduction
as required

• Build the XPath expressions for
the various parts of the
dynamic elements
• Check existence & value
(against configured test data)

Validate Storefront (5)
• Validate the item Price
• Click on the image (NOT Quick
View link)
• Instantiate ItemDetailPage
• Validate ItemDetailPage (local
method)

Validate Storefront (6)
• Validate existence of elements on ItemDetailsPage
• Validation of values – left for interested reader
(see Page Object)

Validate Login (1)
• Validate Account login (local
method)
• Instantiate Account Page
• Validate content existence
• Validation of values – left for the
interested reader

Validate Login (2)
• Local method that does Asserts (assumes valid
credentials)
• Click the Sign-In “label” on the Main Page
• Instantiate Sign-In/(Account Creation) Page
• Validate content existence
• Values – left for interested reader (see Page
Object)
• Enter the email specified by parameter
• Enter the password specified by parameter
• Click the Sign-In button
• Instantiate the Account Page
• Wait for the Account Page to appear
• Existence & Values – left for interested reader
(see Page Object)

Results
• Execution in VS Test Explorer
• We don’t execute “create account” tests as no
means to remove created accounts

Zalenium Test Execution
• Undefine runtime param
in UT code
• -> leads to Config of
RemoteWebDriver
(base class method call)

Zalenium Test Execution
• Batch files (execute in cmd.exe):
• Pull down the most recent images
• Start Zalenium via Docker
• There are a range of configuration parameters that
can be used when starting Zalenium
(see: https://opensource.zalando.com/zalenium/)

Zalenium Test Output
• Example execution: Account Page

Summary
Where are we?

Key Points
Below are the main points to be borne in mind about test automation
The code we produce should reflect development
practice – not the outcome of cooking Spaghetti!
It’s Development
The focus of what we do should be establishing
“correctness” of the application in the context of
each test.
It’s Testing
The tests we write must execute routinely attributes
– particularly when we go to a DevOps pipeline.
It’s Reliable
01
02
03
Tests must meet up to these key attributes –
particularly when we go to a DevOps pipeline.
It’s Maintainable, Accessible, Scalable
04

This slide pack has covered the basic Selenium-based testing validation for a
specific web application, a shopping site. Some of the detail, such as ensuring the
values of things on the individual pages, has been “left to the interested reader”,
as they say. All the methods to do this are available in the individual Page Objects.
We have looked at a subset of testing targets for this site, but in doing so we have
arrived at a scalable testing approach which can be readily expanded.
The use of generated Page Object classes is a key take-away of this presentation.
If, as test automation practitioners, we want to be players in the Agile project story,
then what we do must be “sprintable” - able to be broken down, confidently, into
Stories. The generation of finished Page Objects is key to achieving this worthy
goal.
Two themes when using Selenium:
• Perform exploratory testing on the app to understand how it fits together
• Be prepared to wait for pages and elements (and sometimes element content)
in your test code
This slide pack is one in a series related to Selenium-based test automation.
Summary

Thank you
All views…All voices…All welcome
https://www.linkedin.com/in/david-harrison-2952187/

High sierra part 1

Recommended

Recommended

More Related Content

Similar to High sierra part 1

Similar to High sierra part 1 (20)

More from David Harrison

More from David Harrison (20)

Recently uploaded

Recently uploaded (20)

High sierra part 1