How manual testers can break into Test Automation without programming skills

Transcription

1 How manual testers can break into Test Automation without programming skills Jim Trentadue Enterprise Account Manager - Ranorex jtrentadue@ranorex.com

2 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 3 3

4 Test Automation Industry Recap

5 Test Automation Industry Recap» First Record \ Playback tools appeared about 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 5

6 Test Automation Industry Recap» Below is an evolution of Test 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) 6

7 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: 8

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 9

10 Review of an Automated Test Lifecycle Methodology (ATLM)

11 Mapping an ATLM against an SDLC E. Integration and Test B. Business Analysis and Requirements D. System Design & Development C. Small Tool Pilot/Prototype Illustration of how typical activities of an ATLM align with SDLC activities F. Production and Maintenance A. System Life-Cycle Process Automated Software Testing: Introduction, Management and Performance Dustin, Rashka, Paul 11

12 Categorizing the Areas Required for Test Automation

13 Working Categories for Test Automation Grouping activities in Preparation, Execution & Analysis 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 Execution Learning how objects are recognized within test automation Working with the object repository and organizing this Building test automation actions from the ground up Adding errorhandling in your testing flow Knowing how to step into test cases and debug Reading report results and interpreting this Analysis 13

14 Nine Areas for Manual Testers to Work on Within Test Automation

15 Preparation Planning test automation activities into your testing process Test Automation activities: Project Initiation Outline the scope of automation in the Release Test Plan Test Strategy Analysis Divide test scenarios: Automated vs. Manual Test Scenarios Design Prepare the automated test workflow with error-handling (new and regression) Test Cases Develop Record your modules, ensuring all objects have been recognized Test Scripts Testing Replay until test executes as expected Test Results Deploy Check-in CM Test Summary 15

16 Preparation Creating data sheets or SQL statement for data-driving your automation MyApplication Login ID Password SQL data retrieval SELECT * from Logins where LoginType = Manager Excel example Login ID Password LoginType Simplified Data-Driven setup in a Test Automation solution TestUser1 Password123# Standard User TestUser2 Password456% Supervisor TestUser3 Password789$ Manager 1. Create a variable on what you want to data-drive 2. Link to your data source where the data will be 3. Map your data source columns to the defined variables 16

17 Preparation Editing existing manual test cases for automation 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 Concentrate on just two areas for editing 1. Test Steps 2. Test Data Test Results Best practice to separate your results from any planning info Results will fail automatically if recordings/validations don t match 17

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

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 19

20 Execution Building test automation actions from the ground up 1. Record all of your steps first 2. Focus on a quality recording, not naming each test case first and knowing the initial content TC1: Desktop TC1.1: Start App TC1.2: Add User TC1.3: Close App TC2: Web TC2.1: Open Browser TC3: Mobile TC2.1: Start App TC2.2: Navigate Desktop Web Mobile 20

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? Robust Error- Handling Objects are delayed in appearing in the automated test run? Additional steps need to be added to your test automation recording? 21

22 Analysis Adding error-handling in your testing flow Typical options for debugging automated test cases Debugging allows you to watch where exactly the test case may have issues. This could be with the application or the test recording Set your breakpoint Chose the Step for the breakpoint Execute the test case to Breakpoint 22

23 Analysis Sample manual test case, includes both planning steps and execution results Reading report results and interpreting this 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 23

24 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 25

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 26

27 Thank you for attending! Jim Trentadue Enterprise Account Manager- Ranorex