How Manual Testers Can Break into Test Automation Without Programming Skills

Jim Trentadue

Account / Sales Manager - Ranorex

jtrentadue@ranorex.com

Agenda

3

Agenda

» Test Automation Industry recap

» Test Automation Industry outlook

» Review of an Automated Test Lifecycle Methodology (ATLM)

» Three categories of supporting and working in Test Automation:

» Preparation, Execution and Analysis

» Nine areas for manual testers to work on within Test Automation

» Session recap

Test Automation Industry Recap

5

Test Automation Industry Recap

» First Record \ Playback tools appeared about 20-25 years ago

» The primary objective was to test desktop applications. Some tools could test broken URL links, but not dig into the objects

» The tester was required to have scripting or programming knowledge to make the tests run effectively, even in Record \ Playback

6

Test Automation Industry Recap

» Below is an evolution of Test Automation Frameworks:

Record \Playback

Structured Testing

(invokes more

conditions)

Data DrivenKeyword

Driven

Model / Object Based

Actions Based

Hybrid(combines 2 or more of

the previous frameworks)

Test Automation Industry Outlook

8

Test Automation Industry Outlook

» Number of test automation tools have increased to over 25-30, primarily focused on taking the scripting / programming out of the equation for the manual testers

» Technical complexities have increased considerably to cover the following:

9

Test Automation Industry Outlook

» License models now offer a Test Execution only component, apart from the license to create and maintain the automated tests and object repository

» Tools have the capability to integrate with various Continuous Integration tools and Test Management solutions

Review of an Automated Test Lifecycle Methodology (ATLM)

11

Mapping an ATLM against an SDLC

Automated Software Testing: Introduction, Management and Performance – Dustin, Rashka, Paul

Illustration of how typical activities of an ATLM align with

SDLC activities

D. System Design & Development C. Small Tool Pilot/Prototype

A. System Life-Cycle Process F. Production and Maintenance

B. B

usi

ne

ss A

na

lysi

s a

nd

Re

qu

ire

me

nts

E.

Inte

gra

tio

n a

nd

Te

st

Categorizing the Areas Required for Test Automation

13

Working Categories for Test Automation

• Planning test automation activities into your testing process

• Creating data sheets or SQL statements for data-driving your tests

• Editing existing manual test cases for automation

Preparation

• Learning how objects are recognized within test automation

• Working with the object repository and organizing this

• Building test automation actions from the ground up

Execution • Adding error-handling in your testing flow

• Knowing how to step into test cases and debug

• Reading report results and interpreting this

Analysis

Grouping activities in Preparation, Execution & Analysis

Nine Areas for Manual Testers to Work on Within Test Automation

15

Preparation

Outline the scope of automation in the Release Test Plan

Divide test scenarios: Automated vs. Manual cases

Prepare the automated test workflow with error-handling (new and

regression)

Record your modules, ensuring all objects have

been recognized

Replay until test executes as

expected

Check-in to CM solution

Planning test automation activities into your testing process

Project Initiation

Test Strategy

Analysis

Design

Develop

Testing

Deploy

Test Scenarios

Test Cases

Test Scripts

Test Results

Test Summary

Test Automation activities:

16

Preparation

Login ID Password LoginType

TestUser1 Password123# Standard User

TestUser2 Password456% Supervisor

TestUser3 Password789$ Manager

Excel example

• Login ID

• Password

MyApplication

SELECT * from Logins where LoginType = Manager

SQL data retrieval

3. Map your data source columns to the defined

variables

2. Link to your data

source where the

data will be

1. Create a variable on what you want to

data-drive

Simplified Data-Driven setup in a Test Automation solution

Creating data sheets or SQL statement for data-driving your automation

17

Preparation

Test Steps

• Limit the verbiage to just Actions and Events / Sequences

• 1. Mouse Click

• 2. Key Sequence Value

Test Data

• Avoid hard-coding any values unless mandatory

• Better to maintain to controlled data in an external format

Test Results

• Best practice to separate your results from any planning info

• Results will fail automatically if recordings/validations don’t match

Concentrate on just two areas for editing1. Test Steps2. Test Data

Editing existing manual test cases for automation

18

Execution

• Login ID

• Password

MyApplication

Learning how objects are recognized within test automation

19

Execution

Working with the object repository and organizing this

Features form

» Buttons

» Download Free Trial button

» Join a Free Webinar button

Pricing form

» Buttons

» Links

» Edit Boxes

Support form

20

Execution

Building test automation actions from the ground up

Desktop

Web

Mobile

TC1: DesktopTC1.1: Start AppTC1.2: Add UserTC1.3: Close App

TC2: WebTC2.1: Open

Browser

TC3: MobileTC2.1: Start AppTC2.2: Navigate

1. Record all of your steps first 2. Focus on a quality recording, not

naming each test case first and knowing the initial content

21

Analysis

Adding error-handling in your testing flow

What happens if…

An unexpected window appears in the middle of the

test?

Objects are moved, added, removed or changed?

Objects are delayed in appearing in the automated

test run?

Additional steps need to be added to your test automation

recording?

Robust Error-Handling

22

Analysis

Adding error-handling in your testing flow

Typical options for debugging automated test cases

Set your breakpoint

Chose the ‘Step’ for the breakpoint

Execute the test case to Breakpoint

Debugging allows you to watch where exactly the test case may have issues.

This could be with the application or the test recording

23

Analysis

Reading report results and interpreting this

Sample manual test case, includes both planning steps and execution results

Sample test automation result file shows execution results, but links to the recordings. Information in the run below:

System information like:o Execution time, machine name, operating system,

screen dimensions, language, duration, total errors and total warnings

Global parameter values Ability to Jump to the failed step Total number of iteration runs and report on each data

element Container of screenshot information along the

execution

Session Recap

25

Session Recap

» The Test Automation industry focused on desktop, but is driving to multi-technology stacks to cover a large amount of platforms

» Primary skillset for those working in test automation was Programming or Scripting, but solutions are available for those without these skills

» Map a Test Automation methodology to existing SDLC or Testing workflow processes; same general structure would apply

26

Session Recap

» Understand where your contributions to the test automation initiative are mapped to – either Preparation, Execution or Analysis

» Review the areas where manual testers can work in, focusing on automation structure, object recognition and results interpretation

Say Hello to Truly Automated Awesomeness!

ranorex.com/why

Jim Trentadue

Account / Sales Manager - Ranorex

jtrentadue@ranorex.com