When you start learning QTP, the first question which comes into mind is “how and from where to start”, any prerequisite’s before I start QTP. Frankly speaking, some basic knowledge of VB script will help.
Coming back to QTP, before moving to actual thing, let’s start with some theoretical part of QTP and testing.
So let’s try to answer the “where to start” part…
Analyzing Your Application
The first step would be analyzing your application and determine your testing needs, before you start creating a QTP test script.
First, 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.
Analyzing your application also requires determining the environment in which your application controls were developed, for example web, the language used for development (Java or .NET), so that you can load the required Quick Test add-ins.
Understand the application, so that you could determine the functionality that you want to test. Go through the business processes and understand it in detail, go through the requirement documents and other application document.
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?
Try breaking your processes (functionality) into smaller units, which will be represented by your test’s actions. Each action should emulate an activity that a customer might perform when using your application
As you plan, try to keep the amount of steps you plan to include in each action to a minimum. Creating small, modular actions helps make your tests easier to read, follow, and maintain.
Preparing the Testing Infrastructure
To put in order 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 (we will discuss this later) containing test objects, function libraries containing functions that enhance QuickTest functionality, and so on.
Apart from these, you also need to configure QuickTest according to your testing needs and this include setting up your global testing preferences, your run session preferences, any test-specific preferences, and recovery scenarios.
Finally, you create tests that serve as action repositories in which you can store the actions to be used in your tests.
Generally, you create an action repository test for each area of your application to be tested. Storing all of your actions in specific tests enables you to maintain your actions in a central location. When you update an action in the action repository, the update is reflected in all tests that contain a call to that action. When you run a test, only the relevant action repository tests are loaded. You then associate the shared object repositories with the relevant actions. This enables you to later insert steps using the objects stored in the object repositories. When you create your tests, you insert calls to one or more of the actions stored in this repository.
Adding Steps to Your Actions
You can create steps using the keyword-driven functionality available in the table-like, graphical Keyword View—or you can use the Expert View, if you prefer to program steps directly in VBScript.
Drag objects from your object repository or from the Available Keywords pane to add keyword-driven steps in the Keyword View or Expert View. The object repository and Available Keywords pane contain all of the objects that you want to test in your application.
When you drag an object into the Keyword View, a step is created in the action with the default operation for that object. For example, if you drag a button object into the Keyword View, the click operation is automatically defined for the step. You can then modify the step as needed.
Next step would be record your application. As you navigate through your application during a recording session, QuickTest graphically displays each step you perform as a row in the Keyword View. A step is something that causes or makes a change in your application, such as clicking a link or image, or submitting a data form. In the Expert View, these steps are displayed as lines in a test script (VBScript). The Documentation column of the Keyword View also displays a description of each step in easy-to-understand sentences.
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.
• Broaden the scope of your test by replacing fixed values with parameters.
• Add user-defined functions by creating function libraries and calling their functions from your test.
• Use the many functional testing features included in QuickTest to enhance your test and/or add programming statements to achieve more complex testing goals.
Running and Debugging Your Test
After you create your test, you can perform different types of runs to achieve different goals.
• Run your test to debug it
• Run your test to check your application.
• Run your test to update it.
Analyzing Test Results and Reporting Defects
After you run your test, you can view the results of the run in the Test Results window. You can view a summary of your results as well as a detailed report. Infect this s one of the most important part of your testing cycle, after all this is what goes to customer and based on which the release of application is decided.
No comments:
Post a Comment