Browse Prior Art Database

FVT Script Creation Automation

IP.com Disclosure Number: IPCOM000012365D
Original Publication Date: 2003-May-01
Included in the Prior Art Database: 2003-May-01
Document File: 2 page(s) / 42K

Publishing Venue

IBM

Abstract

FVT test scripts can automatically be created from a test matrix using a converstion tool

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 2

FVT Script Creation Automation

       One type of FV test or functional verification test consists of testing the functionality of an Application Programming Interface (API), which in our case is device driver API's. There are many aspects of a FV test that can be automated to help a test run more efficiently. One way to do a FV test is to write test matrices and from those write scripts. The test matrices are in a structured format that defines the FV test cases, it is an easy way of creating and maintaining test cases. The scripts are written to automate the execution of the test cases that are defined in the test matrices. Matrix's and Script creation are both done manually and can be very time consuming.

     There is very little to be gained from a tester creating the scripts since most of the creativity takes place in the matrix's creation stage. The time it takes to create a script manually is the problem that this idea solves. It is possible to create a conversion tool that can take a test matrix's as input and convert it into a test Script automatically.

     There are four advantages to this. First off, and the most important reason is there will be a 50% savings in time during prep for any new matrices and scripts because script creation will be automated. Secondly, it will cut down on the learning curve for reading matrices because it will set standard rules for how they are written. Third, if any changes need to be made to test cases during a test it will ensure that the changes are made in both the matrix's and scripts at the same time, this prevents costly maintenance fees after the test is over. A fourth advantage to this idea is that it will let the user choose which TC's will be added to a script with very little effort.

Below is a design on how script creation automation can be achieved:

     The test matrices will be created using a lotus 123 spreadsheet, which will be converted into a .CSV file. A .CSV file is a text format that will be used so...