Browse Prior Art Database

Automated Pervasive Device Testing Tool

IP.com Disclosure Number: IPCOM000014496D
Original Publication Date: 2000-Mar-01
Included in the Prior Art Database: 2003-Jun-19
Document File: 2 page(s) / 111K

Publishing Venue

IBM

Abstract

Presently there is no Automated way to test pervasive devices. Pervasive devices are an emerging technology. This tool is designed to be an Automated Test Server for Pervasive devices. It will allow multiple users to develop and run multiple tests on multiple devices in an easy to use manner. Tests can be grouped into Test Buckets with looping options provided to allow for long duration tests to be executed and tracked in an automated fashion. Automated testing of Pervasive devices will be required in many manufacturing operations. This tool is designed to be flexible enough to allow any kind of pervasive device to be tested.

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 61% of the total text.

Page 1 of 2

Automated Pervasive Device Testing Tool

Presently there is no Automated way to test pervasive devices. Pervasive devices are an emerging technology. This tool is designed to be an Automated Test Server for Pervasive devices. It will allow multiple users to develop and run multiple tests on multiple devices in an easy to use manner. Tests can be grouped into Test Buckets with looping options provided to allow for long duration tests to be executed and tracked in an automated fashion. Automated testing of Pervasive devices will be required in many manufacturing operations. This tool is designed to be flexible enough to allow any kind of pervasive device to be tested.

The following is a sample of the User Interface. The Top of the client area allows users to create, update, delete and execute Test buckets. The center section allows users to specify which pervasive devices to execute the tests on, specify how many times to loop on the test, allows the user to specify a test name, runs the specified test and add the test to the test bucket being edited. The bottom section is used to show the tests organized in a tree, display information about the test, allow parameters to be entered for the execution of the test and allows the user to update the list of tests.

The next illustration of the user interface allows the user to see the results of test execution and see what is queued to be performed next. The top section shows a list of links to the logs of the tests which...