0% found this document useful (0 votes)
134 views

Automation Testing: Prepared By: Thanh Nguyen Trung Huynh Phu Last Update: August 2004

This document provides an overview of automation testing and GUI automation. It discusses why testing tools are used, the differences between manual and automated testing, types of tests that can and cannot be automated, and how GUI tests are automated through test scripts, GUI maps, and interacting with the application under test. A variety of automation testing tools are also listed.

Uploaded by

suduku007
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
134 views

Automation Testing: Prepared By: Thanh Nguyen Trung Huynh Phu Last Update: August 2004

This document provides an overview of automation testing and GUI automation. It discusses why testing tools are used, the differences between manual and automated testing, types of tests that can and cannot be automated, and how GUI tests are automated through test scripts, GUI maps, and interacting with the application under test. A variety of automation testing tools are also listed.

Uploaded by

suduku007
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 23

Automation Testing

Prepared by: Thanh Nguyen


Trung Huynh Phu
Last update: August 2004
Objective

 To give an overview of automation test, GUI


automation.
Agenda

 Why use testing tool


 Differences between manual and automated
testing
 GUI and Command Line Test
 Testing tools
 Notes
Why use testing tool

No Testing Manual Testing Automated Testing


• Time consuming  Speed
• Low reliability  Repeatability
• Human resources  Programming
• Inconsistent capabilities
 Reliability
 Reusability
Which test cases can
be automated?

Tests that need to be run for every build of


the application (sanity level, Regression test)
Tests that use multiple data values for the
same actions (data driven tests)
Tests that require detailed information from
application internals (e.g., SQL, GUI attributes)
Stress/load testing
More
Morerepetitive
repetitiveexecution?
execution?
Better
Bettercandidate
candidatefor
forautomation.
automation.
Which test cases can’t
be automated?
Usability testing
 "How easy is the application to use?"
One-time testing
"ASAP" testing
 "We need to test NOW!"
Ad hoc/random testing
 based on intuition and knowledge of
application
Tests without predictable results
Improvisation
Improvisationrequired?
required?
Poor
Poor candidate
candidatefor
forautomation.
automation.
Manual to Automated
Testing
Repeat steps
Wait for Verify AUT until all
Perform user
processes to functions as applications are
actions
complete expected verified
1 2 3 compliant 4

1 2Synchronize 3 4
Generate
script Add Run
Run test
test or
or
automated
playback to verification suite
suite of
of tests
tests
script
application
performance
GUI Test Automation

 What is GUI Test


 Graphical User Interface (GUI) Testing
 Methods used to identify and conduct GUI tests,
including the use of automated tools
 Three Major Elements
 Test script
 GUI map objects
 Application Under Test (AUT)
 Capture and playback.
GUI Test Automation
Real object is
identified and
the specified
AUT
GUI MAP actions taken
place on the
AUT
Controls/Objects
GUIobject
GUI object11
LogicalName
Logical Name
{
{
Physical descriptions
Physical descriptions
} Get the
}
…………… physical
…………… The TSL command
GUIobject
GUI objectn:n: descriptions of completely
the object to executed. Proceed
identify it. next command
TEST SCRIPT
WR check if
Find the TSL 1 (GUI Object, other parameters); the actions
physical …………………………………………….. would be
descriptions of TSL n (GUI Object, other parameters); performed on
the specified the real
GUI object application
Interactive Test
Automation

 Test requires interactive steps


 Via console, CLI
 Use command language: TCL, Expect, Perl,
Unix shell…
Testing Tools
 SilkTest
 WinRunner & Xrunner
 Expect/TCL/TK
 QARun
 QA Partner
 QC/Replay
 Evaluator
 CAPBAK
 Vermont High Test Plus
 WITT
 ATS/X-Tester
 etc
Notes

 Problem
 Test Set
 Report
 Tool Support
 Batch Test
 Time Management
 Cleaning up
Problem

 Unstable system
 Changing
 Real observation
 Different environment
 etc
Test Set
Example:
Example:

ASF Project
Objective:
Tungsten Perform an integrated test
on the NHA application.
Single System
CLI
WebUI
Protocol Determine order of test
… execution:
1. Create Customer
M .. Complaint Log
A Mics 2. Process Customer Log
3. Update Customer Log
HA System
Multiple iSDs
Protocol
Report

 Text
 Graph
 Email
 User-Defined
Tool Support

 Existing tool
 Developing tool
Batch Test

 Run from command line


 Invoke from other tool
 Invoke from other system
 Platform Independent
Time Management

 Timeout
 Time Waiting
Cleaning up

 Restore to fresh environment


 Not effect to the next test case
ASF Automation tool
ASF Automation tool
Test result
Q&A
Thank you!

You might also like