Quick Test Professional; Introduction

Quick Test Professional

Introduction

Mercury interactive Quick test professional is a sophisticated testing tool. QTP is much more powerful then Win runner and you can migrate to it very easily. Like Win runner, QTP is also a functional/ regression testing tool that can be used to generate various test cases and run them automatically. Its important features are given below:

It has the record/ replay provision to record the user interactions with the application software. You can record your keyboard entries and mouse clicks of application GUI. QTP automatically generates the test script. You can run the test script repeatedly for regression testing of your application. The testing tool has a recovery manager and in case the application halts due to an error, is will automatically recover ñ this is very useful for unattended testing. It uses VB script as the scripting language and its syntax is very similar to visual basic, hence learning this scripting language is very easy. QTP provides checkpoint options. It provides a facility for synchronization of test cases. Its ‘auto documentation’ feature provides the feature of creating test documentation. Test report data is stored in documented XML format. This facilitates transferring the report data to another third party tool. It supports Unicode and hence you can test applications written for any of the world languages. Using special add-in modules, you can use QTP for testing a variety of applications such as: ERP/ CRM packages .NET web forms, win forms, .NET control Multimedia applications

Quick Test Professional; Introduction

Quick Test Professional

Introduction

Mercury interactive Quick test professional is a sophisticated testing tool. QTP is much more powerful then Win runner and you can migrate to it very easily. Like Win runner, QTP is also a functional/ regression testing tool that can be used to generate various test cases and run them automatically. Its important features are given below:

It has the record/ replay provision to record the user interactions with the application software. You can record your keyboard entries and mouse clicks of application GUI. QTP automatically generates the test script. You can run the test script repeatedly for regression testing of your application. The testing tool has a recovery manager and in case the application halts due to an error, is will automatically recover ñ this is very useful for unattended testing. It uses VB script as the scripting language and its syntax is very similar to visual basic, hence learning this scripting language is very easy. QTP provides checkpoint options. It provides a facility for synchronization of test cases. Its ‘auto documentation’ feature provides the feature of creating test documentation. Test report data is stored in documented XML format. This facilitates transferring the report data to another third party tool. It supports Unicode and hence you can test applications written for any of the world languages. Using special add-in modules, you can use QTP for testing a variety of applications such as: ERP/ CRM packages .NET web forms, win forms, .NET control Multimedia applications

Recording a Test Case

Quick Test Professional

Recording a Test Case

In the recording mode, QTP captures all the operations performed on the GUI. You need to work with the application in the usual way and record all the actions. While recording a Test case, QTP captures all the images of various actions. It then generates the test script for the actions performed in VBScript language. There are three modes of recording a test case:

Normal recording mode: Default mode of recording. Analog recording mode: this mode is used when exact mouse positions or keystrokes play an important role in recording. Low level recording mode: This mode of recording enables you to record on the objects even if Quick test professional fails to identify the object.

This section describes how to record the process of making a reservation for a flight.

Start Quick test and open a new test Choose START>PROGRAMS>QUICK TEST PROFESSIONAL>QUICK TEST PROFESSIONAL Start recording on the mercury tour website. Choose TEST>RECORD or click the RECORD button. 3. Login to mercury tours web site. In the user name and password boxes, type user name and password you registered with mercury tools. Click sign in The flight finder page opens. Enter flight details. Select a flight Click CONTINUE to accept the default flight selections. The book a flight page opens. Enter required passenger and purchase information. Review and complete your booking. Stop recording. Save your test Select FILE>SAVE or click SAVE button.

Running Tests

Quick Test and open the recording test. Confirm that all images are saved to the test results. Start running your test. Click Run or choose Test>Run. The run dialog box opens. Select new run results folder. Click Ok to close the run dialog box.

CREATING CHECKPOINTS

Quick Test Professional

CREATING CHECKPOINTS

A checkpoint verifies that expected information is displayed in your application while running the test.

Understanding checkpoints types Checking objects Checking pages Checking text Checking tables Running and understanding a test with checkpoints

Understanding checkpoints types:

Quick test professional offers the various types of checkpoints given in the table below. You can add most checkpoints to your test either while recording or afterward. When quick test professional creates a checkpoint, it assigns a name based on information inside the checkpoint- the checked value. For example, the checkpoint name remains unchanged, even if you subsequently modify the information on which it was based.

Check point Type Description Example of use Standard Checkpoint checks values of objects properties Check that a radio button is selected. Image Checkpoint checks property value of an image Checks that image source file is correct. Table Checkpoint Checks information in table Checks that the value in a table cell is correct. Page Checkpoint Checks the characteristic of a web page. Checks how long a web page takes to load. Text /Text area Checkpoints Checks that the pages string is displayed in the appropriate place. Checks whether the expected text script is displayed in the expected location on a web page. Bitmap Checkpoint Checks an area of a web page. Checks that a web page for any portion is displayed as expected. Database Checkpoint Checks the content of database Checks that the value in a database query is correct. Accessibility Checkpoints identifies areas of website to check Check if the images on a web page include ALT properties. XML Checkpoints Checks the data content of XML document XML checkpoints are used to check specified XML file.

Checking objects:

In this section you will add a standard checkpoint in the book a flight page. This checkpoint will verify the value in the box containing the first name of the passenger.

Start Quick Test and open the recording test. Choose START>PROGRAMS>QUICK TEST PROFESSIONAL>QUICK TEST PROFESSIONAL. If the welcome window opens, click OPEN EXISTING. If the Quick test opens displaying the welcome window, choose FILE> OPEN. Save the test as checkpoint. Select FILE> SAVE AS. Save the test as checkpoint. Confirm that active screen option is enabled. If you do not see the active screen on the right side of the Quick Test window, click the active screen toolbar button or choose view> active screen. Locate the page where you want to add a standard checkpoint. Create a standard checkpoint. In the active screen, right click the first name and choose Insert Standard Checkpoint. The object selection- checkpoint properties dialog box opens. The checkpoint dialog box opens. The dialog box displays the object’s properties. The logical name is the name of the object. The class is the type of object. The ABC icon in the type column indicates that the value of the property is a constant. Accept the default settings and click OK. Quick Test adds a standard checkpoint step to your test. Save the test Choose FILE> SAVE or click the SAVE button.

Checking Pages:

In this section, you will add a page checkpoint to your test. The page checkpoint checks that the number of links and images in the page when you run the test is the same as when you recorded your test.

Locate the page where you want to add a page checkpoint. Create a page checkpoint. Right click anywhere in the active screen and choose INSERT STANDARD CHECKPOINT. The object selection- checkpoint properties dialog box opens. This dialog may include different elements, depending on where you click on the active screen. When you run the Quick test, It checks the number of links and images in this page and the load time, as described in the pane at the top of the dialog box. Quick test also checks the actual target URL of each link and the actual source of each image. Accept the default settings and click OK. Quick test adds the page checkpoint to your test. Save the test Choose FILE> SAVE or click SAVE button.

Checking Tables:

In this section you will add a table checkpoint to check the cost as the outbound flight page.

Locate the page where you want to add a table checkpoint. Create a table checkpoint. In the active screen, right click the price displayed for the first flight and choose INSERT STANDARD CHECKPOINT. The object selection- checkpoint properties dialog box opens. Select web table- New York to San Francisco. The table checkpoint properties dialog box opens, showing the rows and columns of the table. Save the test Choose FILE> SAVE or click SAVE button.

Running and analyzing a test with checkpoints:

Expand the test tree and review your test. Choose VIEW> EXPAND ALL. The test tree will be displayed. Start running your test. Click Run or choose TEST>RUN. The run dialog box opens. Select new run results folder. Accept the default results folder name. Click OK. When the test run is completed, the test results window opens. View the test results When Quick Test Professional finishes running the test, the test results window opens. The test result should be passed, indicating that all checkpoints are passed. If one or more checkpoints had failed, the test result would be failed. View the result of the page checkpoint. In this test tree, expand (+) checkpoint iteration row 1 (Row 1)> action summary> welcome> mercury> book a flight. In this you can review the details of the page checkpoints, which list the items checked. View the results of table checkpoints. In this test tree, Book a flight: page, expand (+) New York to. In this, you can review the values of the table cells. View the results of standard checkpoints. In this test tree, Book a flight: page, expand (+) pass first0. In this, you can review the details of the standard checkpoints, which list the properties that were checked. View the results of the text checkpoint. In this test tree, expand (+) checkpoint iteration 1 (row 1)>action summary> welcome: mercury>flight conformation. In this, you can review the details of text checkpoints. Close the test results. Choose FILE>EXIT.

CREATING CHECKPOINTS

Quick Test Professional

CREATING CHECKPOINTS

A checkpoint verifies that expected information is displayed in your application while running the test.

Understanding checkpoints types Checking objects Checking pages Checking text Checking tables Running and understanding a test with checkpoints

Understanding checkpoints types:

Quick test professional offers the various types of checkpoints given in the table below. You can add most checkpoints to your test either while recording or afterward. When quick test professional creates a checkpoint, it assigns a name based on information inside the checkpoint- the checked value. For example, the checkpoint name remains unchanged, even if you subsequently modify the information on which it was based.

Check point Type Description Example of use Standard Checkpoint checks values of objects properties Check that a radio button is selected. Image Checkpoint checks property value of an image Checks that image source file is correct. Table Checkpoint Checks information in table Checks that the value in a table cell is correct. Page Checkpoint Checks the characteristic of a web page. Checks how long a web page takes to load. Text /Text area Checkpoints Checks that the pages string is displayed in the appropriate place. Checks whether the expected text script is displayed in the expected location on a web page. Bitmap Checkpoint Checks an area of a web page. Checks that a web page for any portion is displayed as expected. Database Checkpoint Checks the content of database Checks that the value in a database query is correct. Accessibility Checkpoints identifies areas of website to check Check if the images on a web page include ALT properties. XML Checkpoints Checks the data content of XML document XML checkpoints are used to check specified XML file.

Checking objects:

In this section you will add a standard checkpoint in the book a flight page. This checkpoint will verify the value in the box containing the first name of the passenger.

Start Quick Test and open the recording test. Choose START>PROGRAMS>QUICK TEST PROFESSIONAL>QUICK TEST PROFESSIONAL. If the welcome window opens, click OPEN EXISTING. If the Quick test opens displaying the welcome window, choose FILE> OPEN. Save the test as checkpoint. Select FILE> SAVE AS. Save the test as checkpoint. Confirm that active screen option is enabled. If you do not see the active screen on the right side of the Quick Test window, click the active screen toolbar button or choose view> active screen. Locate the page where you want to add a standard checkpoint. Create a standard checkpoint. In the active screen, right click the first name and choose Insert Standard Checkpoint. The object selection- checkpoint properties dialog box opens. The checkpoint dialog box opens. The dialog box displays the object’s properties. The logical name is the name of the object. The class is the type of object. The ABC icon in the type column indicates that the value of the property is a constant. Accept the default settings and click OK. Quick Test adds a standard checkpoint step to your test. Save the test Choose FILE> SAVE or click the SAVE button.

Checking Pages:

In this section, you will add a page checkpoint to your test. The page checkpoint checks that the number of links and images in the page when you run the test is the same as when you recorded your test.

Locate the page where you want to add a page checkpoint. Create a page checkpoint. Right click anywhere in the active screen and choose INSERT STANDARD CHECKPOINT. The object selection- checkpoint properties dialog box opens. This dialog may include different elements, depending on where you click on the active screen. When you run the Quick test, It checks the number of links and images in this page and the load time, as described in the pane at the top of the dialog box. Quick test also checks the actual target URL of each link and the actual source of each image. Accept the default settings and click OK. Quick test adds the page checkpoint to your test. Save the test Choose FILE> SAVE or click SAVE button.

Checking Tables:

In this section you will add a table checkpoint to check the cost as the outbound flight page.

Locate the page where you want to add a table checkpoint. Create a table checkpoint. In the active screen, right click the price displayed for the first flight and choose INSERT STANDARD CHECKPOINT. The object selection- checkpoint properties dialog box opens. Select web table- New York to San Francisco. The table checkpoint properties dialog box opens, showing the rows and columns of the table. Save the test Choose FILE> SAVE or click SAVE button.

Running and analyzing a test with checkpoints:

Expand the test tree and review your test. Choose VIEW> EXPAND ALL. The test tree will be displayed. Start running your test. Click Run or choose TEST>RUN. The run dialog box opens. Select new run results folder. Accept the default results folder name. Click OK. When the test run is completed, the test results window opens. View the test results When Quick Test Professional finishes running the test, the test results window opens. The test result should be passed, indicating that all checkpoints are passed. If one or more checkpoints had failed, the test result would be failed. View the result of the page checkpoint. In this test tree, expand (+) checkpoint iteration row 1 (Row 1)> action summary> welcome> mercury> book a flight. In this you can review the details of the page checkpoints, which list the items checked. View the results of table checkpoints. In this test tree, Book a flight: page, expand (+) New York to. In this, you can review the values of the table cells. View the results of standard checkpoints. In this test tree, Book a flight: page, expand (+) pass first0. In this, you can review the details of the standard checkpoints, which list the properties that were checked. View the results of the text checkpoint. In this test tree, expand (+) checkpoint iteration 1 (row 1)>action summary> welcome: mercury>flight conformation. In this, you can review the details of text checkpoints. Close the test results. Choose FILE>EXIT.

Data driven test

Quick Test Professional

Data driven test

Once the test script is created, you may sometimes want to check how the test script behaves for multiple data. This can be done by creating that many number of test cases and by running each test case individually, which is very difficult. In such cases we use data driven testing. This involves following steps:

Create the test case. Parameterize the test case. Provide the required data. Run the test case. Checking tables

Parameterize test:

When you test your applications, you may want to check how it performs the same operations with multiple sets of data. For example you want to check how your web site responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create data table parameters so that your test runs ten times, each using different set of data. It has four parts:

Defining a data table parameter. Adding parameter values to a data table. Modifying steps affected by parameterization. Running and analyzing tests.

Defining a data table parameter:

In this, we will make departure city (of previous section) a parameter so that you can use a different departure city for each test run.

Start Quick Test and open the checkpoint tests. If Quick test is not already open, choose START> PROGRAMS> QUICK TEST PROFESSIONAL> QUICK TEST PROFESSIONAL. Then choose, FILE> OPEN or click open button. Save the test as parameter Select FILE> SAVE AS. Save the test as parameter. Confirm that active screen option is enabled. If you don’t see the active screen on the right side of the Quick test window, click the active screen toolbar button, or choose VIEW> ACTIVE SCREEN. Confirm that data table option is enabled. If you don’t see the data table at the bottom of the screen, click the data table toolbar button, or choose VIEW> DATA TABLE. Select the text to parameterize. In the test tree, expand (+) action 1> welcome: mercury> find a flight. Right click “from port” select “New York” and select method arguments. The method arguments box opens. Set the parameterization properties. In this case, the method is select because an item was selected from a list. The argument table displays argument properties. The ABC icon indicates that the argument is constant. Item indicates that the argument is a constant. New York is the value of argument. The edit value area is enabled and displays the constant value New York. In the edit value area, select parameter. This lets you replace the constant value (New York) with a parameter. Confirm that he data table option is selected. This means that the value of the parameter will be taken from the quick test data table. The parameter name box is enabled and displays from port_item. Change this departure. Click OK to close the dialog box. Quick Test adds the departure parameter to the data table as a new column and inserts New York in the first row under it. New York will be the first of the several departure cities that Quick Test will use during test runs of the application.

Adding parameter values to a data table

Adding parameter values to a data table

In this, we will add two more departure cities to the data table, so that Quick Test can test the application with this data.

Enter additional cities in departure column. Click row 2 in the departure column and add another city name. For example Portland Click row 3 and add seattle. Press Enter. Save the test Select FILE> SAVE. Or click Save button.

Modifying steps affected by parameterization:

After parameterization of one step in a test, other test objects might be affected when the value of the parameterized step changes. If so, you must modify the expected values of those objects to match the value resulting from the parameterized step. In this, we will modify the text checkpoint so that when running the test, Quick test checks for the text that matches the current departure city.

Locate the text checkpoint to modify. In this parameter test tree, expand (+) welcome: mercury> flight conformation. Right click checkpoint: New York and select checkpoint properties. The text checkpoint properties dialog box opens. Parameterize the text checkpoint. In the checked data area, New York is displayed in the constant box. New York is expected value for the checkpoint for every iteration. Click parameter. In the parameter name box, select departure. This instructs the checkpoint to use the departure parameter values in the data table for the expected results. Click ok. Note that the icon is now displayed beside the checkpoint. This indicates that the checkpoint is parameterized. Save the test. Select FILE> SAVE.

Running and analyzing parameterized test:

You can now run the modified parameter test. Quick Test will run the test for three times, once for each departure city in the data table. Each test run is called iteration.

Run the parameter test. Click run on the Quick Test toolbar or choose TEST> RUN. The run dialog box opens. Select new results folder and accept the default results folder name. Click OK. When the test run is complete, the test results window opens. Examines the results summary. Iteration 2 In this results tree, expand (+) parameter iteration 2> action summary> welcome mercury> flight conformation. The checkpoint results show that Portland was the expected result and the actual result. Therefore the checkpoint is passed. Iteration 3 In this results tree, expand (+) parameter iteration 3> action summary> welcome mercury> flight conformation The checkpoint results show that seattle was the expected result and the actual result. Therefore the checkpoint is passed. Close the test result windows. Choose File> Exit to close the test results window.

Creating output values

In the previous section, we created parameters that inserted different data into each iteration of test run. You can also retrieve data from your application and output it to the data table using output values. This data can be used at later stage in the test. Quick test displays the retrieve data, following the test run, in the runtime data table. For example, you can use an output value to verify that the date or flight no. is correctly displayed in two different web pages, by using the value obtained in one page as the expected text that Quick Test checks in for other page.

Creating an output value

In this you will create an output value that retrieves the outbound fare from the select a flight page in each test iteration.

Start Quick Test and open the parameter tests. If Quick test is not already open, choose START> PROGRAMS> QUICK TEST PROFESSIONAL> QUICK TEST PROFESSIONAL. Then choose, FILE> OPEN or click open button. Save the test as output Select FILE> SAVE AS. Save the test as output. Confirm that active screen option is enabled. If you don’t see the active screen on the right side of the Quick test window, click the active screen toolbar button, or choose VIEW> ACTIVE SCREEN. Select the text you want to use as an output value. In the test tree, expand (+) welcome: mercury and click select a flight page. This page is displayed in active screen. In this active screen, highlight the fare, without $ sign. Right click the highlighted text and select insert text output. The text output values properties dialog box opens. Set the output value option. The data table column name box displays select_a_flightoutput_text_out. Change this to depart_flight_price. Click ok to accept the other default settings. Quick test adds the depart_flight_price column to the data table. Modify the table checkpoint that checks the ticket price is displayed in the flight summary table. In the test tree, expand (+) welcome: mercury> book a flight. Right click checkpoint “New York to” and select checkpoint properties. The table checkpoint properties dialog box opens. Click column 3 in row 3 (the checked cell). In the check value as area, click parameter and the depart_flight_price from the parameter name box. Click OK. Save the test. Select FILE>SAVE or click save button.

Running and analyzing a test with output values

Now we will run the test and examine the results.

Run the output test. Click run on the Quick Test toolbar or choose TEST> RUN. The run dialog box opens. Select new results folder and accept the default results folder name. Click OK. When the test run is complete, the test results window opens. Examine the run time data results. In the test results window, select run time data from the results tree. The output values used during the test run are displayed in a grid. Note that a different price is shown in the depart_flight_price column for each iteration. Examine the checkpoint results. Choose view> expand all. In the output iteration 1 (row 1), under “book a flight” page, click checkpoint “New York to”. In the details pane, the checkpoint is marked in green as passed because the price of the ticket for the first flight in the summary table matched the expected value obtained from select a flight page. Examine the checkpoints for iteration 2 and 3 as well. Close the test results window. Choose file> exit to close the window.

Using regular expressions

We can use the regular expressions to increase the flexibility and acceptability of your tests.

Regular expression syntax

Regular expression enables Quick test to identify objects and text strings with varying values. You can use regular expressions when defining the properties of an object, the method of an arguments, when parameterize a step, and when creating checkpoints with varying values. A regular expression is a sting that specifies a complex search phase. By using special character such as a period (.), asterisk (*), caret (^), and brackets ([]).

Working with regular expressions

Start Quick Test and open the recording tests. If Quick test is not already open, choose START> PROGRAMS> QUICK TEST PROFESSIONAL> QUICK TEST PROFESSIONAL. Then choose, FILE> OPEN or click open button. Save the test as Regular expression. Select FILE> SAVE AS. Save the test as parameter. Confirm that active screen option is enabled. If you don’t see the active screen on the right side of the Quick test window, click the active screen toolbar button, or choose VIEW> ACTIVE SCREEN. Select the text for which you will create the checkpoint. In the test tree, expand (+) welcome: mercury and click the select a flight page. The page is displayed in the active screen. In the active screen, scroll up and highlight the date, for the outbound flight. Right click the highlighted text and select insert text checkpoint. The text checkpoint properties dialog box opens. Enter the regular expression for the text you want to check. In the checked text area, click the edit constant options button. The constant value options dialog box opens. In value box replace the current date. This instructs Quick test to check that each character is selected text matches the number range format defined by regular expression. The expression checks for the following format: mm/dd/yyyy. Select the regular expression check box. A message prompts you to insert the backlash character before each special character. Click no. Click ok to accept other default settings and close the constant value options dialog box. Save the test. Select FILE> SAVE or click Save button.

Running and analyzing a test with regular expressions

Run the regular expression test. Click run on the Quick Test toolbar or choose TEST> RUN. The run dialog box opens. Select new run results folder and accept the default results folder name. Click OK. When the test run is complete, the test results window opens. Examine the checkpoint results. In the results tree, expand (+) test regular expression summary> regular expression iteration 1 (row 1)> action summary> welcome: mercury> select a flight. The checkpoint passed because the text was displayed in the format specified by the regular expressions. Exit the test result window. Choose File> Exit to close the test result window.

Dividing tests into multiple actions

Actions divide your test into logical sections. When you create a new test, it contains one action. By dividing your tests in to multiple actions, you can design more modular and efficient tests.

Creating new actions

Start Quick Test and open a new test. Choose START> PROGRAMS> QUICK TEST PROFESSIONAL> QUICK TEST PROFESSIONAL Start recording on the mercury tour website. Choose TEST> RECORD or click the RECORD button Login to mercury tours web site. In the user name and password boxes, type user name and password you registered with mercury tools. Click sign in The flight finder page opens. Enter flight details. Select a flight Click CONTINUE to accept the default flight selections. The book a flight page opens. Enter required passenger and purchase information. Enter the required information in passenger and credit card sections. Return the browser to the flight finder page. At the bottom of the flight conformation page, click back to flights button. The flight finder page opens. Stop recording In Quick test, click stop to stop the recording process. Save the test Select File> Save as.

Dividing the test into two actions

Select the page where you want the second action begin in the test tree, expand (+) action 1> welcome: mercury. Split the test in to two actions. Select the find a flight page and choose step> split action or click the split action toolbar button. The split action dialog box opens. Enter the names and description for the two actions.

Inserting new action

Insert the return home action. Choose Insert> New action or click the insert new action toolbar button. The insert new action dialog box opens. Enter return home in the name box, confirm that at the end of the test is selected and click OK. Prepare the application for recording. Confirm that your web browser is open to the flight finder page. Position the applications on your desktop so that you can see both Quick test and web browser. Change the record and run settings. Record the return home action. In the tree view, select the new return home action icon. Return the record and run settings to their original settings. Save the test Choose File> Save as