2.Testing Process

The Quick Test Testing Process consisting of the following min phases to convert our selected manual Functional Testing cases into Automation Test Script:

o Planning

o Creating Tests or Component.

o Inserting Checkpoints into your test or components.

o Debugging Test Script.

o Running the Test Script.

o Analyzing the Result.

o Reporting Defects.

2.1. Planning:

Before starting to build a test, you should plan it and prepare the required infrastructure.

For example, determine the functionality you want to test, short tests that check specific functions of the application or complete site.

Decide how you want to organize your object repositories.

2.2. Creating Tests or Component:

We can create test or component by

a.) either recording a session on your application or web site.

As we navigate through the application or site, Quick test graphically displays each step we perform as a row in the keyword view. The documentation column of the keyword view also displays a description of each step in easy-to-understand sentences. A step is something that causes or makes a change in your site or application, such as clicking a link or image, or submitting a data form.

(Or)

b.) build an object repository and use these objects to add steps manually in the keyword view or Expert view. We can then modify your test or component with special testing options and/or with programming statements.

2.3. Inserting checkpoints into your test or components:

A checkpoint is a verification point that compares a recent value for a specified property with the expected value for the property. This enables you to identify whether the web site or application is functioning correctly.

2.4. Debugging Test Script:

Broaden the scope of your test or component by replacing fixed values with parameters.

To check how your application performs the same operations with different data you can parameterize your test or component.

When you parameterize your test or component, Quick Test substitutes the fixed values in your test or component with parameters

Each run session that uses a different set of parameterized data is called an iteration.

We can also use output values to extract data from our test or component. An output value is a value retrieved during the run session and entered into the Data Table or saved as a variable or a parameter. We can subsequently use this output value as input data in your test or component.

We can use many functional testing features of Quick Test to improve your test or component and/or add programming statements to achieve more complex testing goals.

2.5. Running the Test Script:

After creating test or component, we run it.
Run test or component to check the site or application.
When we run the test or component, Quick Test connects to your Web site or application and performs each operation in a test or component, checking any text strings, objects, or tables you specified. If we parameterized the test with Data Table parameters, Quick Test repeats the test (or specific actions in your test) for each set of data values we defined.

Run the test or component to debug it.

We can control the run session to identify and eliminate defects in the test or component. We can use the

Step Into,

Step Over,

And Step Out commands to run a test or component step by step. We can also set breakpoints to pause the test or component at pre-determined points. We can view the value of variables in the test or component each time it stops at a breakpoint in the Debug Viewer.

2.6. Analyzing the Result:

After running the test or component, we can view the results of the run in the Test Results window. We can view a summary of the results as well as a detailed report.

2.7. Reporting Defects:

If Quality Center is installed, we can report the defects fond out to a database. We can instruct Quick test to automatically report each failed step in the test or component, or we can report them manually from the Test Results window.