An Automation Framework for Everyone

1

Strategic Talent Management 1

© 2015 Halogen Software Inc. Confidential – Not to be used, copied or redistributed without Halogen’s prior written permission.

An Automation Framework for Everyone

Wednesday May 6th, 11:30am Presented by: Chris Loder



• Who, what, where…

• Abstraction Layer

• Config files

• Our State Machine

• Using conditions

• Our version of key word approach

− Test Case Example

− Page object Example

• Getting Results

• Questions

Agenda

2

Who, what, where…



Who?

• Who am I?

−I am the guy between you and

lunch!

3



5

Industry leader in customer satisfaction

>450Employees

Growing Global Employee Base

>2,000Customers

Growing Global Customer Base

Customer Successes

What?Halogen: Industry Leader in Talent Management Systems



Where?

• Where is our Framework used?

−Everywhere in product development

� Automation Developers

� Manual QA

� Product Developers

4

Abstraction Layer



Abstraction Layer

• Why we did it?

− No more rewriting test cases just because the tool has changed!

• Pros

− Makes the framework more robust and gives us the control of what

to expose to our automation developers

− Developers get used to using Halogen’s Framework objects versus

Selenium's

− Ability to change tools is just a handful of classes away

• Cons

− Adds extra maintenance

− We have to be the keepers of all new functionality

5



Abstraction Layer

Config Files

6



Config Files

• Pros

− Flexibility

− Essentially a command line extension

− Extra runtime validation

• Cons

− An extra layer

− Can get out of sync with the framework

• Example



7

Our State Machine



Our State Machine

• Used to handle the “State” of the

element we are working with to

determine successful execution of the

given action.

• Unknown, Element Found, Validating

and Unstable.

• Makes use of our element conditions.

8

Using Conditions



Using Conditions

• Why we have them?

−Stability

− Used and “inline” validation. Particularly

with navigation calls

−We can assign multiple conditions to an

element

−State Machine vs “Wait for Condition”

− Examples….

9



Using Conditions

Our version of the Keyword

Driven approach

10



Our version of the keyword driven approach

• Why?

− Known proven practice

− Speedier automated test case authoring

− Allows just about anyone to write an automated test

• Our approach is page.action

� Basically what page you are on in the application and then what

action you would like to perform on that page

� Examples:

o Responding.goToAdmin();

o Admin.goToCompensation();

o Compensation.openBudgetDefinition(budgetName)

o BudgetDefinition.setBudgetValue(value)



Test Case Example

11



Test Case Example - Continued



Page Class Example

12



Page Class Example - Continued

Getting results

13



Getting results

• Why we wrote our own results manager

− Control

− Easily allows us to send out different result types

− Extendibility

• What we get from it

− Logs

− Test Case Management Tool (APTest / Zephyr)

− XML

− CSV

− Perf

− FancyOutput



Getting results

14



Getting results



Getting results

FancyOutput.html

15

Questions?

An Automation Framework for Everyone

Software

Transcript of An Automation Framework for Everyone