Why Use Testing Tools?
Problem with Manual Testing:
- Time consuming
- Low reliability
- Human resources
- Inconsistent
- Speed
- Repeatability
- Programming capabilities
- Coverage
- Reliability
- Reusability
Automated testing Tool for MS Windows based application.
From Manual to Automated Testing
Which Test Cases to Automate:
- Tests that need to be run for every build of the application (sanity level)
- 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
RapidTest Script Wizard:
Walks through application and learns all windows and objects
Use Comprehensive mode
pauses after each window learned
allows you to modify logical names which appear in test scripts
allows you to map custom objects to standard objects which makes test scripts context sensitive
GUI Map File
the Wizard stores all information in a GUI Map file
for multiple testers, store GUI Map file on a shared network drive
A Closer Look at GUI Objects:
RECORD AND PLAYBACK
What Happens During Recording?
What Happens During Playback?
Two Recording Modes:
Context Sensitive Recording:
- Object oriented
- Readable script
- Maintainable script (editable)
- Script not affected by User Interface changes
if object moves location on GUI, script will still replay correctly - Portable script
a context sensitive script can be ported to different platforms with different configurations
User Actions in the Test Script:
ANALOG vs.CONTEXT SENSITIVE SCRIPTS
Context Sensitive Script Review:
Analog Recording:
Screen-coordinate dependent
Test script describes mouse and keyboard activities
3 commands:
Mouse press/release
Mouse move
Keyboard type
Covers ALL types of applications
Subscribe to this comment's feed
| Next > |
|---|
