Successful Test Automation without Coding. Marc J. Balcer Chief Architect Model Compilers

Size: px

Start display at page:

Download "Successful Test Automation without Coding. Marc J. Balcer Chief Architect Model Compilers"

Marion Stephens
5 years ago
Views:

1 Successful Test Automation without Coding Marc J. Balcer Chief Architect Model Compilers

2 Successful Test Automation without Coding Frequent, continuous automated testing is key to successful agile development. But many teams resist fully automated testing, believing their testers need to have programming expertise in order to build automated tests. While that may have been true at one time, recent advances have made it easier to implement automated testing without coding skills. Join ASPE s test automation expert Marc Balcer for an exploration of the different kinds of automation tools and techniques. Learn how to create a strategy for implementing automation, tips for selecting the appropriate tools, and how to design applications for productive test automation.

com Author of Executable UML and Applied SOA Chief Architect of TAME Test Authoring

3 TAME Test Authoring Made Easy Introduction Marc J. Balcer Founder & Chief Architect Model Compilers Author of Executable UML and Applied SOA Chief Architect of TAME Test Authoring Made Easy ASPE Lead Instructor for Modeling Techniques for Business Analysis Ranorex Test Automation Workshop Test Automation Boot Camp

4 Outline Why Automated Testing? An Automation Example Skills Considerations Building Apps for Automation Tool Considerations

5 Development Models Traditional waterfall Integration infrequent and later in the process Tests run a few times before delivery Tasks complete are the key measure of progress Agile / incremental Continuous integration starting on Day 1 Tests run on every change often several times a day Passing test cases are the key measure of progress Manual testing OK Manual testing impossible

6 Continuous integration Continuous testing Developer makes changes and checks in to the common source base This kicks off a re-build After the build is complete, start running all of the tests ( regression test suite ) Determine that The new build added the new features The new build didn t break anything

7 Frequent Re-testing Standing Army of manual testers Easy Automated testing Harder People need to be on standby Machines run the tests divide and conquer People need to complete before the next build Tests proceed at machine speed Agile speed requirements generally make manual testing impractical.

8 An Automation Example

9 Example: Savings Calculator User enters goal amount amount to be saved each period Calculator figures number of deposits that need to be made Errors need to be handled goal amount 0 periodic savings amount 0

10 Automated Unit Testing Unit = single code function Tests are a program that sets up the environment for each test case call the function compare actual to expected results report pass / fail

11 Automated Unit Testing in Visual Studio

12 Automated Unit Testing in Visual Studio

13 UI Testing?

14 UI Testing? Go to the page. Fill in these boxes. Check these values Click Compute and check that this only shows up if there is a remainder.

15 Expose UI as code

16 Expose UI as code UI elements Actions on the UI elements Validations against the UI elements

17 The Website Test Architecture Unit Testing UI Testing Unit Test Code Unit Test Code Adapters Test Platform Application Code UI Code Application Code

18 Problem? Writing tests is limited to people who can write code.

19 The history of computing is a history of raising the level of abstraction

20 Record Playback Model

21 Record Playback and Validate Too!

22 Record Playback Model UI elements Actions on the UI elements Validations against the UI elements

23 Record Playback Model UI elements Actions on the UI elements Validations against the UI elements

24 Actions User Behavior Click on something Type in text Move the mouse Supporting Behaviors Take a screenshot Write to the log Set a property Validation Does this exist? Do the values match? Replacement Behaviors Do a lower level action when the recorded action doesn t work correctly

25 UI Elements Test actions refer to UI elements by name A repository (or symbol table or dictionary ) maps names to path expressions.

26 Several Recorded Tests Divides goal evenly Does not divide goal evenly

27 Test Suite = many test cases

28 Modular Test Cases

29 Modular Test Suite Test Cases Module containing common steps Unique part

30 Similar Tests by Copy and Paste Test with a zero deposit amount and then with a negative deposit amount

31 Similar Tests by Data Tables

32 Structuring Test Suites Sanity or Smoke test Simple Record-Playback Distinct Combinations

33 Object Identification and Path Expressions

34 Identifying UI Elements Test actions refer to UI elements by name A repository (or symbol table or dictionary ) maps names to path expressions.

35 Simple: Web Elements have IDs UI page On this page find an input item with an ID of MainContent_SavingsGoal HTML

36 Challenging: Not everything has a good unique ID Some objects will have more complex path expressions

37 Path Expression Syntax

38 Windows Forms elements have paths too The adapter model allows the same techniques to be used for different technologies

39 Consider: Your automation environment should support all of your platforms

40 Skills Pyramid Coders Editors Recorders

41 What kinds of Editing? Clean up the recording Modularize Create data-driven tests Build new modules from repository elements Build new test cases from existing modules

42 New Modules from Existing UI Elements Grab the item from the repository 7-5

43 New Modules from Existing UI Elements then place the action in the module. Select the action type / subtype. 7-5

44 New Test Cases from Existing Modules Drag an existing module to a new test case.

45 What Still Requires Coding? Calculate a value (e.g. to compare a result) Perform conditional checking Complex looping External system access Create custom actions

46 Skills Pyramid Coders Editors Recorders

47 Building for Automation

48 Web IDs

49 Random IDs Bad!

50 Standard Controls

51 Tool Considerations

52 Tool Considerations What capabilities do you need? What platforms? Team skills? Multi-user test development and execution?

53 Summary Why Automated Testing? An Automation Example Skills Considerations Building Apps for Automation Tool Considerations

54 Thank you. Questions?

How Can a Tester Cope With the Fast Paced Iterative/Incremental Process?

How Can a Tester Cope With the Fast Paced Iterative/Incremental Process? by Timothy D. Korson Version 7.0814 QualSys Solutions 2009 1 Restricted Use This copyrighted material is provided to attendees of