InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

A Method for Human Interaction in Massive Automation Test

IP.com Disclosure Number: IPCOM000198640D
Publication Date: 2010-Aug-11
Document File: 5 page(s) / 130K

Publishing Venue

The IP.com Prior Art Database


The new idea is a method to accommodate testers to run a dozen of automated test scripts concurrently. We provide a system that automatically collect all the screen/terminal information which need human interactions, and add simple readable description of the act to the screens where the tester is required to input.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 5

A Method for Human Interaction in Massive Automation Test

The new idea is a method to accommodate testers to run a dozen of automated test scripts concurrently as figure 1. Assuming a tester needs to execute 10 or even more test scripts in different machines , it usually requires him to remote desktop /terminal to those machines and monitor the scripts execution status . If the scripts have designated break -points during execution which need human interactions , the tester will need to wait and interact with the scripts . And the tester is required to have the knowledge of the detailed test scripts execution steps, for example, in a testing script of credit card application , in script 1 he should input a date before current date , and in script 2 he should input a date in future . Even if the tester is very familiar with all those scripts , it's still very error prone to switch context among too many scripts .


Page 2 of 5

Figure 1 Massive Automation Test Scenario


[This page contains 1 picture or other non-text object]

Page 3 of 5

Our solution has the following advantages comparing to prior -arts: 1) Improve testing capacity . Whenmonitoring multiple test machines , screen/terminal info are pushed to control machine when human interaction is needed . Manually busy monitoring is abandoned , saving the time of context switching , such as periodically pulling test machine screen /terminal info and checking if human interaction should be started. 2) Lower tester's skill level. With pre-designed readable description , these is no need fortester to understand complete context to proceed, or to worry about whether his /her action is appropriate . Follow screen description is sufficient for test to make the right interaction.

Here we describe how the system works . As shown in the figure 2...