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

Method and system for optimize the execution of tests in a virtual environment

IP.com Disclosure Number: IPCOM000203472D
Publication Date: 2011-Jan-26
Document File: 3 page(s) / 150K

Publishing Venue

The IP.com Prior Art Database


A method and a system is disclosed for optimizing the execution of automated test cases in a virtualized environment. The system automatically provisions/de-provisions the required virtual servers only when needed and orchestrates the concurrent execution of multiple test cases optimizing the overall hypervisor resource utilization.

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

Page 01 of 3

Method and system for optimize the execution of tests in a virtual environment

Nowadays there are plenty of test automation frameworks available in the field that try to satisfy most of the requirements that usually are related to such kind of harnesses, such as tools integration, legacy tools support, easy of use, data integration, reporting features, shell script support, automatic environment setup, remote command execution, and so on.

    When a user is trying to execute a scenario (a test scenario for example), his environment can contains some Virtual Machines with recorded snapshots (for example a Windows XP SP2 machine with a snapshot at SP1 and another at "Base Level").

If he is using another machine with an installed product and he want to test the product on the three different Windows XP service pack states, he had to manually run the test on the machines restoring the state each time or use three different real machines. In these circumstances, the runtime of a snapshot can cover all the life cycle of the scenario or only a predefined time frame.

    Some existing solutions give the possibility to statically setup a Virtual Environment with predefined descriptors but are not able to dynamically manage the machine life cycle snapshots optimizing the VM hypervisor resources. The core of the proposed solution is to have a system (Test Manager System ) that is able to receive scenario configuration files describing the machine interactions at specific snapshot states. Detailed information about the snapshot life cycles can be used to increase the parallelism and to optimize the resource allocation.

    A test scenario can generally be defined by the description of the environment ( impacted machines) and actions to performed on them (tests to be executed).

    In the solution described herein, a Test Scenario can be described with a Configuration file (an XML for example) containing both the instructions for running the test scenario and some additional information such us the machine's state (snapshots) and the machine's life cycle (start and stop commands) for specifying how the test environment should evolve over time.

    The Test Scenario Configuration file contains the workflows (general actions that can be performed among the machines), the different states (S1, …, SN) and start/stop actions to setup and tear down the virtual machines snapshots. The

workflows can be executed in sequence or in parallel and a VM machine can appear

more than one time in the workflows with different states. It is up to the "Test Manager System" to decide how to parallelize the execution of multiple test scenarios and to manage the VM allocation/de-allocation according to the definitions of the scenarios and to the availability of VM resources.For example in a typical configuration file, a given machine A may be referenced as A(S1


     (for specifying each machine's snapshot) and the machine life cycle instructions could be specified as start[A(S1

or stop[...