Automated Testing TipsAutomated Testing Tips

Copyright © 2000 Compuware Corporation

Mark NesslarJuly 15, 2000

2 of 11

Test types

Record and Playback Structural Data Driven

3 of 11

Lessons learned

Jell-O and the Electric Dog

4 of 11

Communication

Testers Automation Specialist Development Management

3 to 10 times

5 of 11

Automated testing is development

Programming Knowledge Planning Standards Discipline Well documented Not easy, Not cheap

6 of 11

Automation Specialist

Design Develop Test Debug Document code

7 of 11

What to test

Repeatable Expected results

8 of 11

Do a test run

OS Browser Platform

9 of 11

Know the application

Know the requirements Know issues EEK! Third Party Controls Break it up

10 of 11

Scripting

Keep it small Each test should be a beginning,

middle, end

11 of 11

What makes a good script?

CommentedWill not change much Tests something that needs to be

testedHandles ErrorsEasily Understood

12 of 11

I can do that (the programmer dilemma).

Oh, that’s good Oh, that’s bad (don’t automate what

is highly complex) Keep the focus on testing

13 of 11

Functions

Application Functions Company Functions

14 of 11

Functions

Know the FunctionsLibraryAvoid duplicationNew people

15 of 11

Structure

ScriptsDriver

Subject (Test Case)– Scripts (reusable, static)

Functions

16 of 11

Error processing

Take a screen print Save it to a file Write message to log file Close and re-open app for next test

Loop to close all windows Can’t account for everything so

account for that

17 of 11

Tricky tools

Comments Checks How would you test it manually?

18 of 11

Header of Default Script Programming Information What does script do Limitations Requirements Environments Global Variables Company functions Application functions

19 of 11

Staffing

Tools don’t replace testers, testers doBWI

20 of 11

Automation

Start Small Be disciplined Develop standards Understand Application Do the preliminary work

Script like a mad dog

21 of 11

Data Driven

Minus: Takes a lot of time Need a programmer Requires good communication with

development Plus:

Reusable across applications Easy for Testers to Write

22 of 11

Data Driven

Write a function for each possible action

Navigation Scripts Spreadsheet test cases Build a switch case

23 of 11

mark.nesslar@compuware.com