Building a Test Automation Framework · ─Example “core” framework •Assumptions ─You understand what test automation is (and isn’t) ─You understand why a “framework”

Building a Test Automation FrameworkTHE BASICS

COPYRIGHT UTOPIA SOLUTIONS, INC.1

About Us…

Brett Haase• Test Automation Architect• Works with many clients / Engagements• Nearly 20 years in industry• Makes Great Omelets• Award winning STEM Toy Creator


Email: [email protected]: @brett7threeLinkedIn: linkedin.com/in/bretthaase

Hemant Ojha• Sr. Test Automation Engineer• Almost 10 years industry experience• Pragmatist• Adventure sports lover• Occasional Skydiver

Email: [email protected]: @hemanto22LinkedIn: linkedin.com/in/ojhahemant

mailto:[email protected]:[email protected]

Building a Test Automation Framework• What will this webinar address?

─ Framework architecture─ Questions to answer while building a framework─ Key components of a framework─ Example “core” framework

• Assumptions─ You understand what test automation is (and isn’t)─ You understand why a “framework” is necessary


Typical Framework ArchitectureCommon Framework Components• Required

─ Test engine

─ Reporting

─ Browser Driver & Wrappers

─ API Testing Client

─ Dependency / Build Management

• Recommended─ Logging

─ Browser Hosting

─ Assertion Library

─ BDD Tools (if doing BDD in general)

─ Data Management


Choosing a Language

• Key criteria to consider─ Prevalent skills on the team

─ Availability of required libraries

─ Language of application under test


Test Engine

Why a test engine?─ Manage tests─ Manage pre / post test

execution actions─ Group / categorize tests─ Reporting / logging


Browser Drivers & Wrappers

• Selenium is powerful, but has limitations─ Synchronization

─ Complex element interactions

─ AJAX support


API Testing Support

• Rest Assured / Karate / etc.• Why UI and API in the same

framework?─ Reuse of common framework

components─ Easy access to data setup via API─ Promotes testing at the appropriate

layer


CoreFramework ConfigurationReporting

Data ManagementUtilities

Reporting• Key reporting capabilities

─ Well organized results─ Inclusion of test artifacts (screenshots,

attachments, etc.)─ Historical data / trends─ Filtering and sorting


Extent Reports

Allure

Build Tool

• Build Tool Responsibilities─ Dependency management─ Code packaging─ Running tests / generating

reports─ Deployment


Other Components


CI/CD Support & Framework Extensibility


Sample FrameworkHIGH LEVEL WALKTHROUGH


Framework Core & Sample Application


FRAMEWORK CORE SAMPLE APPLICATION PROJECT

DEPENDENCY

Framework Core as a Dependency


Writing Tests


Fluent Approach

The Classic Way

Test Results – Extent Reports


Questions…


…. and Answers!

Direct future questions to:

Brett HaaseTest Automation ArchitectUtopia Solutions, Inc.

Email: [email protected]: @brett7threeLinkedIn: linkedin.com/in/bretthaase

?Hemant OjhaSr. Test Automation EngineerUtopia Solutions, Inc.

Email: [email protected]: @hemanto22LinkedIn: linkedin.com/in/ojhahemant

Utopia Solutions Framework Corehttps://github.com/UtopiaSolutions/UtopiaSolutionsFWCore

A Sample Application and Java projecthttps://github.com/UtopiaSolutions/SampleApplication
mailto:[email protected]:[email protected]://github.com/UtopiaSolutions/UtopiaSolutionsFWCorehttps://github.com/UtopiaSolutions/SampleApplication

Documents

Building a Test Automation Framework · ─Example “core” framework •Assumptions ─You understand what test automation is (and isn’t) ─You understand why a “framework”