Adoption of automating tests has not happened as quickly as organizations need. As more companies move toward implementing agile development as their software development lifecycle, more features are being implemented and released more quickly. This leaves less time for full regression testing of the system, nonetheless this should still be done. Manual testers need to transform into test automation testers as well. Learn how to make this jump as a manual tester and focus on the right areas first e.g. automation test structure, object recognition and results interpretation.

1. HowManualTestersCan
BreakintoTestAutomation
WithoutProgramming
Skills
JimTrentadue
Account / Sales Manager - Ranorex
jtrentadue@ranorex.com

2. Agenda

3. 3
Agenda
» Test Automation Industry recap
» Test Automation Industry outlook
» Review of an AutomatedTest Lifecycle Methodology
(ATLM)
» Three categories of supporting and working inTest
Automation:
» Preparation, Execution and Analysis
» Nine areas for manual testers to work on withinTest
Automation
» Session recap

4. TestAutomationIndustryRecap

5. 5
TestAutomationIndustryRecap
» 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. 6
TestAutomationIndustryRecap
» Below is an evolution ofTest Automation
Frameworks:
Record
Playback
Structured
Testing
(invokes
more
conditions)
Data Driven
Keyword
Driven
Model /
Object
Based
Actions
Based
Hybrid
(combines 2
or more of
the previous
frameworks)

7. TestAutomation IndustryOutlook

8. 8
TestAutomationIndustryOutlook
» 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. 9
TestAutomationIndustryOutlook
» License models now offer aTest 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 andTest Management
solutions

10. ReviewofanAutomatedTest
LifecycleMethodology(ATLM)

11. 11
MappinganATLMagainstanSDLC
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. SmallTool Pilot/Prototype
A. System Life-Cycle ProcessF. Production and Maintenance
B.BusinessAnalysisandRequirements
E.IntegrationandTest

12. CategorizingtheAreasRequiredfor
TestAutomation

13. 13
WorkingCategoriesforTestAutomation
• 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

14. NineAreasforManualTesterstoWork
onWithinTestAutomation

15. 15
Preparation
Outline the scope of automation in the ReleaseTest 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. 16
Preparation
Login ID Password LoginType
TestUser1 Password123# StandardUser
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 aTest Automation solution
Creating data sheets or SQL statement for data-driving your automation

17. 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 editing
1. Test Steps
2. Test Data
Editing existing manual test cases for automation

18. 18
Execution
• Login ID
• Password
MyApplication
Learning how objects are recognized within test automation

19. 19
Execution
Working with the object repository and organizing this
Features form
» Buttons
» Download FreeTrial button
» Join a FreeWebinar button
Pricing form
» Buttons
» Links
» Edit Boxes
Support form

20. 20
Execution
Building test automation actions from the ground up
Desktop
Web
Mobile
TC1: Desktop
TC1.1: Start App
TC1.2:Add User
TC1.3: CloseApp
TC2:Web
TC2.1: Open
Browser
TC3: Mobile
TC2.1: StartApp
TC2.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. 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. 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. 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

24. SessionRecap

25. 25
SessionRecap
» TheTest 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 aTest Automation methodology to existing
SDLC orTesting workflow processes; same general
structure would apply

26. 26
SessionRecap
» 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

27. SayHellotoTruly
Automated
Awesomeness!
ranorex.com/why
JimTrentadue
Account / Sales Manager - Ranorex
jtrentadue@ranorex.com