Testing Process Workflow

The general workflow of the QuickTest testing process, involves the following main stages:

• Stage 1: Analyzing Your Application
• Stage 2: Preparing the Testing Infrastructure
• Stage 3: Adding Steps to Your Actions
• Stage 4: Enhancing Your Test
• Stage 5: Running and Debugging Your Test
• Stage 6: Analyzing Run Results and Reporting Defects

Stage 1: Analyzing Your Application

Before you begin creating a test, you need to analyze your application and determine your testing needs. You need to:

• Determine the development environments in which your application controls were developed, such as Web, Java, or .NET, so that you can load the required QuickTest add-ins.
• Determine the functionality that you want to test. To do this, you consider the various activities that customers perform in your application to accomplish specific tasks. Which objects and operations are relevant for the set of business processes that need to be tested? Which operations require customized keywords to provide additional functionality?
• Decide how to divide these processes into smaller units that will be represented by your test’s actions. Each action should emulate an activity that a customer might perform when using your application.

Stage 2: Preparing the Testing Infrastructure

To complete the infrastructure that is part of the planning process, you need to build the set of resources to be used by your tests, including shared object repositories containing test objects (which are representations of the objects in your application), function libraries containing functions that enhance QuickTest functionality, and so on.

Stage 3: Adding Steps to Your Actions

In this stage, you add steps to the actions in your test action repository. Before you begin adding steps, make sure that you associate your function libraries and recovery scenarios with the relevant tests, so that you can  insert steps using keywords.

Stage 4: Enhancing Your Test

You can enhance the testing process by modifying your test with special testing options and/or with programming statements, such as:

• Insert checkpoints and output values into your test.
• You can also use output values to extract data from your test. An output value is a value retrieved during the run session and entered into your data table or stored in a variable or a parameter. You can subsequently use this output value as input data in your test.
• Broaden the scope of your test by replacing fixed values with parameters.

Stage 5: Running and Debugging Your Test

After you create your test, you can perform different types of runs to achieve different goals.

Stage 6: Analyzing Run Results and Reporting Defects

After you run your test, you can view the results of the run in the Run Results Viewer. You can view a summary of your results as well as a detailed report. If you captured still images or movies of your application during the run, you can view these from the Screen Recorder tab of the Run Results Viewer.

Test Your  Automation Testing Skills By Taking Our Free Practice Tests On This Link