Browse Prior Art Database

A System of Configuring Execution for Business Scenario Test Cases

IP.com Disclosure Number: IPCOM000191218D
Original Publication Date: 2009-Dec-21
Included in the Prior Art Database: 2009-Dec-21
Document File: 3 page(s) / 18K

Publishing Venue

IBM

Abstract

Disclosed is a system of configuring application execution for business scenario test cases

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 3

A System of Configuring Execution for Business Scenario Test Cases

Most software applications are required to run on different operating systems with different supporting hardware/software configurations. Some applications need to run on more than 5 operating systems. In order to cover these combinations during software test, it often requires installing an operating system and the required supporting software applications for each of the

particular mix. In testing this kind of software applications, the developers are facing several

issues:


Setting up test environments is time consuming. Most of the time, large amounts of the work is spent on setting up the test environment, not the test itself.

Running tests often messes up the test environment. Sometimes restoring test environments to a clean state takes as much time as setting it up initially.

Test cases usually have descriptions about the operating system and supporting software requirements. Finding out the exact hardware/software combinations from test descriptions and making sure all the combinations are covered are very time consuming.

These issues not only exist in software application testing, but also exist in business scenarios, building demo machines and sale planning. A more desired situation is that each part in a test environment is a pluggable piece whether it's a piece of software or hardware. Then setting up a test environment becomes a matter of picking the right pieces and putting them together. This method will solve the 1st and the 2nd issue. Then the solution to the 3rd issue is just a matter of developing a tool to read the test description and output a list of required pieces.

Some existing technologies have already provided solutions to these issues to a certain degree. Virtualization technologies allow snapshots of a system to be taken at different times. Different snapshots can be saved for different configurations. However, it does not provide the flexibility at the level of granularity that is needed to support the plug and play configuration.

A system is proposed here called a Virtual System Configurator (VSC). The system consists of a tool called Virtual System Test Case Reader (VSTCR) that reads test cases to produce descriptions of needed configurations. The descriptions are fed into another tool called the Virtual System Description Reader (VSDR). The purpose of the virtual system description reader is to interpret the configuration descriptions that were produced, into a catalog of virtual disk components in support of assembling the desired test solution required. Based on the descriptions, virtual disks with the right level of software are pulled together and assembled into a complete virtual machine image ready for provisioning into a target hypervisor. VSC can also capture 'delta' virtual disks fro...