automated testing, test case generation, software testing

 Home Contact Us FAQ Site Map

About Us Products Solutions Support

Up | Example 1 | Example 2 | Pairwise Testing

Example 2

System Configuration Test example

 

Here is another example to illustrate how SmartTest works using System Configuration testing: 

Suppose you have an application that needs to be tested on several hardware and software configurations.  You are told that the application must be able to run on a Windows NT, Windows 2000 and Windows XP machine.  It also has to work on a system with a minimum of 128Meg and a max of 512Meg of RAM.  Finally, the application must also run on a Pentium II, III, and IV processor and work with Oracle, SQL and Access Databases.

For this example our input set is as follows:

 

OPERATING SYSTEM

RAM

PC PROCESSOR

DATABASE

Windows NT

128Meg

Pentium II

Oracle

Windows 2000

256Meg

Pentium III

SQL

Windows XP

512Meg

Pentium IV

Access

 

For this example there are 3x3x3x3=81 possible System Configuration test combinations.So which combinations should be tested?  How do you know that you have tested all necessary combinations?  How do you ensure that you haven’t missed any combinations?

Let SmartTest do the work:

Step 1.  Enter in the test input.

The information from the table above is entered into SmartTest in the test input tab:

 

 

Step 2.  Enter in Business Rules (if any).

Lets assume that Windows XP cannot run on a Pentium II PC Processor.  We need to create a rule to ensure that we do not have any tests with Windows XP on a Pentium II. This is done in the Rules Builder:

 

 

 

Our rule is - Exclude: If the OPERATING SYSTEM is Windows XP And the PC PROCESSOR is PENTIUM II.

The Rules tab will display the newly created rule:

 

                       

 

 Step 3. Generate Tests.

Simply click on the Generate Tests button and the test cases are generated:

 

 

 

The test results window indicates that we would normally have 81 exhaustive tests.  SmartTest has determined that only 8 optimized tests are needed!