CAST & LTAC & which tests to automate


Been a while since I posted anything, so here is a couple of quickies.

 I’ll be giving a Keynote at CAST 2007 on Testing Software Services.  Originally I thought of doing a double entendre about Testing of Web services and Services for Testing software like SDT’s Unified TestPro® but I found there is so much more to say about testing of web services, that I will focus only on that.

 Google sponsored the London Test Automation Conference (LTAC) in Sept. 2006 where they videod lots of non-Google people talking about automated testing:     http://video.google.com/videosearch?q=LTAC&hl=en

 

I found this paper on “A way of Improving Test Automation Cost-Effectiveness”  in the free CAST 2006 proceedings, page 24, and thought it might be of interest (I also like their list of references).  It provides something I hear frequently asked for.
             
It offers a viability analysis method, to help testers decide which tests can be automated cost-effectively.
In particular they reduce it down to a decision tree (see below).

I also liked “EPDAV – A Model for Test Case Definition” on page 50 for its clarity. 

Perform a verification,                             Vv
which may be preceded by a sequence of actions, A
a
which may require a set of data,              D
d
which may require preconditions,           P
p
all of which runs in environment,            Ee

Turning this notation around so that it can be read from left to right, we get:

A Test Case, Tt = Ee Pp Dd Aa Vv

The above is a different take on Expect This from Test Drivers (p5 on Test Impl Notes)

S – Setup
E – Execution
A – Analysis
R – Reporting
C – Cleanup
H – Help

An automated test case has SEARCH.  (From my 1992 paper How to Automate Testing – The Big Picture.  )

 And finally, page 133, “The Personal Test Maturity Matrix” (another flavor of Microsoft’s Career Stage Profiles or even the Testers Body of Knowledge, originally from James Bach, and adapted to BEA.)

               

Table 1. Questions for each point

Identifier

Topics

Related Questions

1

Frequency

How many times is this test supposed to be executed?

2

Reuse

Can this test or parts of it be reused in other tests?

3

Relevance

How would you describe the importance of this test case?

4

Automation Effort

Does this test take a lot of effort to be deployed?

5

Resources

How many members of your team should be allocated or how expensive is the equipment needed during this test’s manual execution?

6

Manual complexity

Is this test difficult to be executed manually?
Does it have any embedded confidential information?

7

Automation tool

How would you describe the reliability of the automation tool to be used?

8

Porting

How portable is this test?

9

Execution effort

Does this requires a lot of effort to be executed manually?

  TestAutoDecisionTree.jpg

 

Advertisements

About testmuse

Software Test Architect in distributed computing.
This entry was posted in software testing. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s