Browse Prior Art Database

A Correlative Test Plan Model for Various Test Stages Disclosure Number: IPCOM000199941D
Publication Date: 2010-Sep-21

Publishing Venue

The Prior Art Database


A holistic Test Plan Model which can encapsulate various test stages and whcih dervies the colleration of the test cases to re-use test execution components can highly optimize test execution cycles. This article desribes a scheme for creating test cases for various Test Stages in Testing cycles while discovering correlations and levergaing them. Convertors are employed based on the correlations present in the Test Plan Model to generate the test cases only once and tranform them for execution in other test stages.

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

Page 1 of 10

A Correlative Test Plan Model for Various Test Stages

Disclosed is a method to create test cases for only one stage of testing and to obtain the test cases for other stages through in-built logic oriented conversions from one Test Case Format to other as required by each stage. The scheme proposed here targets on reducing the time and effort spent on creating test plans and translating each of them to get sets of test cases for each stage. This reduces the time and effort spent on re-writing test cases for every stage and enhances the accuracy of test cases too.

A typical Test Plan involves various stages like Functional Verification Test(FVT), User Interface Test(UIT), Technical Test(TT), Global Verification Test(GVT) and their automation. Each of these stages involves a separate Test Plan Model which is translated to produce stage specific test cases. These test cases are then pushed to the test framework via appropriate tool for execution. This methodology involves redundant steps where the same test scenarios are re-written in different formats for different stages of testing. Existing schemes for Test Plan involve separate preparation of Test Case Sets for every stage individually.

The proposed scheme to achieve the above mentioned idea is to create a single master Test Plan which can be used for test case generation for each test stage. Instead of generating test cases for each stage from the individual test case plan, it is proposed that the translation from test case model to the test cases should only be done once for the stage which is the super set of all other stages. Typically it is proposed that the first translation should be done for FVT.

Once the set of test cases is prepared for the super set stage, this set can be converted directly to obtain sets of test cases for other stages. This test case to test case conversion can be achieved with the help of converters designed on the basis of rules defined in the test plan model itself. These converters need to be prepared only once for a service scenario, after which all the test cases of sub-set stages can be automatically generated. This conversion of test cases of one stage to another will be automatic, hence saving all the time and effort required for generating them one by one via direct translation from test plan model.

One more advantage of the above conversion model is that once accuracy of the master set of test cases and that of the converter is established, accuracy of the derived test cases obtained for other stages via conversion becomes certain. The Executor is an enhanced rules engine which orchestrates the execution of the whole test plan.

The crux of the technique proposed can be broken down into the following steps:

1. The first step is to create a single holistic master Test Plan which can be used for test case generation for each test stage, instead of creating separate Test Plan for every stage.
2. The test stage which covers maximum number of tes...