Testing Your Own Application with QTP—Getting Started
You shall follow the procedure outlined below when testing your own application.
Plan your test.
Decide how to organize your test. Consider what users will want to accomplish when deciding which operations to record. Confirm that your application and QuickTest are set to match the needs of your test.
Decide how to store the objects in your test. You can store the objects for each action in its corresponding local object repository, or you can store the objects for each action in one or more common (shared) object repositories. You can also use the same shared object repository for multiple actions.
If you are new to testing, you may want to use a local object repository for each action. This is the default setting, and all objects are automatically added to the local repository of each action.
If you are familiar with testing, it is probably most efficient to work in the shared object repository mode. In this mode, you can use shared object repositories for one or more actions. This means that object information is kept in one central location. When the objects in your application change, you can update them in one location for multiple actions in multiple tests.
For more information on object repositories, refer to the Mercury QuickTest Professional User's Guide.
Record your test.
While recording follow the steps you expect users to perform as they navigate within your application or Web site.
Enhance your recorded test.
Add checkpoints to search for specific values of a page, object, text string, or table.
Replace fixed values in your test with parameters to check how your application performs the same operations with multiple sets of data.
Create output values to retrieve data during a test run.
Where applicable, use regular expressions to increase the flexibility and adaptability of your tests.
You can further enhance your test with programming and conditional and loop statements, which add logic to your test. These are described in the QuickTest Professional User's Guide.
Debug your test.
Debug your test to check that it operates smoothly and without interruption. For additional information on debugging, refer to the Mercury QuickTest Professional User's Guide.
Run your test.
Run your test on your application or Web site to check that the application functions as expected.
Analyze the test results.
Examine the results of your test to pinpoint defects in your application. (Refer to the appropriate sections of this tutorial to understand what to look for in the test results.)
Report defects.
If you have Quality Center installed, you can submit any defects discovered to a Quality Center database. (Quality Center is Mercury Interactive's tool for software test management).
For additional information, refer to the Mercury QuickTest Professional User's Guide and the documentation included with Quality Center.
Wednesday, July 30, 2008
Quick Test Professional(QTP)- Part 1
QTP is best available tool for Functionality Testing. I am starting series of posts on this tool. In this post I am just trying to cover QTP introduction and in next posts I will try to cover further topics.
QTP features:
1. Key word driven testing:
We can record one script and parameterize it for different inputs to verify whether the application works as expected for all the classes of inputs.
2. Suitable for both client server and web based application.
The Tool can be used to test both Client Server and different Web Based Applications.
3. VB script as the script language:
Win Runner uses Test Script Language which is specific to WR but QTP uses VB Script. If you know VB Script then you can enhance or edit your test script.
4. Better error handling mechanism:
5. Excellent data driven testing features.
Advantages of QTP:
1.QTP allows even novice testers to be productive in minutes. You can create a test script by simply pressing a Record button and using an application to perform a typical business process. Each step in the business process is automated documented with a plain-English sentence and screen shot. Users can easily modify, remove, or rearrange test steps in the Keyword View.
2.QTP can automatically introduce checkpoints to verify application properties and functionality, for example to validate output or check link validity. For each step in the Keyword View, there is an ActiveScreen showing exactly how the application under test looked at that step. You can also add several types of checkpoints for any object to verify that components behave as expected, simply by clicking on that object in the ActiveScreen.
3.You can then enter test data into the Data Table, an integrated spreadsheet with the full functionality of Excel, to manipulate data sets and create multiple test
iterations, without programming, to expand test case coverage. Data can be typed in or imported from databases, spreadsheets, or text files.
4.Advanced testers can view and edit their test scripts in the Expert View, which reveals the underlying industry-standard VBScript that QuickTest Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.
5.Once a tester has run a script, a TestFusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test script
specifying exactly where application failures occurred, the test data used,application screen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint pass and failure. By combining TestFusion reports with Mercury Quality Management, you can share reports across an entire QA and development team.
6.QTP also facilitates the update process. As an application under test changes, such as when a ?Login? button is renamed ?Sign In,? you can make one update to the
Shared Object Repository, and the update will propagate to all scripts that reference this object. You can publish test scripts to Mercury Quality Management, enabling other QA team members to reuse your test scripts, eliminating duplicative work.
7.QuickTest Professional supports functional testing of all popular environments, including Windows, Web, .Net, Visual Basic, ActiveX, Java, SAP, Siebel, Oracle, PeopleSoft, terminal emulators, and Web services.
QTP features:
1. Key word driven testing:
We can record one script and parameterize it for different inputs to verify whether the application works as expected for all the classes of inputs.
2. Suitable for both client server and web based application.
The Tool can be used to test both Client Server and different Web Based Applications.
3. VB script as the script language:
Win Runner uses Test Script Language which is specific to WR but QTP uses VB Script. If you know VB Script then you can enhance or edit your test script.
4. Better error handling mechanism:
5. Excellent data driven testing features.
Advantages of QTP:
1.QTP allows even novice testers to be productive in minutes. You can create a test script by simply pressing a Record button and using an application to perform a typical business process. Each step in the business process is automated documented with a plain-English sentence and screen shot. Users can easily modify, remove, or rearrange test steps in the Keyword View.
2.QTP can automatically introduce checkpoints to verify application properties and functionality, for example to validate output or check link validity. For each step in the Keyword View, there is an ActiveScreen showing exactly how the application under test looked at that step. You can also add several types of checkpoints for any object to verify that components behave as expected, simply by clicking on that object in the ActiveScreen.
3.You can then enter test data into the Data Table, an integrated spreadsheet with the full functionality of Excel, to manipulate data sets and create multiple test
iterations, without programming, to expand test case coverage. Data can be typed in or imported from databases, spreadsheets, or text files.
4.Advanced testers can view and edit their test scripts in the Expert View, which reveals the underlying industry-standard VBScript that QuickTest Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.
5.Once a tester has run a script, a TestFusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test script
specifying exactly where application failures occurred, the test data used,application screen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint pass and failure. By combining TestFusion reports with Mercury Quality Management, you can share reports across an entire QA and development team.
6.QTP also facilitates the update process. As an application under test changes, such as when a ?Login? button is renamed ?Sign In,? you can make one update to the
Shared Object Repository, and the update will propagate to all scripts that reference this object. You can publish test scripts to Mercury Quality Management, enabling other QA team members to reuse your test scripts, eliminating duplicative work.
7.QuickTest Professional supports functional testing of all popular environments, including Windows, Web, .Net, Visual Basic, ActiveX, Java, SAP, Siebel, Oracle, PeopleSoft, terminal emulators, and Web services.
Tuesday, July 29, 2008
Testing Principles
1. A good test case is one likely to show an error.
2. Description of expected output or result is an essential part of test-case definition.
3. A programmer should avoid attempting to test his/her own program.
testing is more effective and successful if performed by an Independent Test Team.
4. Avoid on-the-fly testing. Document all test cases.
5. Test valid as well as invalid cases.
6. Thoroughly inspect all test results.
7. More detected errors implies even more errors present.
8. Decide in advance when to stop testing.
9. Do not plan testing effort under the tacit assumption that no errors will be found.
10. Testing is an extremely creative and intellectually challenging task.
2. Description of expected output or result is an essential part of test-case definition.
3. A programmer should avoid attempting to test his/her own program.
testing is more effective and successful if performed by an Independent Test Team.
4. Avoid on-the-fly testing. Document all test cases.
5. Test valid as well as invalid cases.
6. Thoroughly inspect all test results.
7. More detected errors implies even more errors present.
8. Decide in advance when to stop testing.
9. Do not plan testing effort under the tacit assumption that no errors will be found.
10. Testing is an extremely creative and intellectually challenging task.
Wednesday, July 23, 2008
Load Runner for Functionality Testing?
Load Runner is a Performance Testing Tool, but Load Runner allows us to parameterize the test scripts. By using Parameterization we can use Load Runner for Regression Testing.
In order to conduct Regression testing using Loadrunner you need to create a script and parameterize it.
Example: You want to check the functionality of login window using 10 different users. For this you will have to follow the following procedure:
1. Record the script using any valid user.
2. Open the script and create parameters for username and password.
3. Fill in the values for the parameters in the flat file.
4. Change the values of paramters on every iteration.
5. Run the script for 10 iterations.
How to Parameterize a test script in Load Runner?
Select the text to be parameterized->R-click on that text you will have a option called Replace with parameter(click)->Here you will be creating a new parameter . In this you will have to the parameter name and when you click on properties, you will get one more pop up window in which you can create a table and add rows so that you give as parameters(values to be substituted when script is run) as you want.
Notice that when this process is finished your selected text will be replaced with the parameter name you gave and that will be in a pair of flower brackets & also in some different color.
Next time onwards in the same script, if you want to parameterize another text, when you right click you will be able to see the option 'Use Existing Parameter'. And you can include as many parameters as you want also you can paramterize with the same parameter.
To view the parameter substitution while replaying go to RunTime Settings->Log->Enable->Extented Log->Parameter Substitution
This is how you will be able to do regression testing using loadrunner.
In order to conduct Regression testing using Loadrunner you need to create a script and parameterize it.
Example: You want to check the functionality of login window using 10 different users. For this you will have to follow the following procedure:
1. Record the script using any valid user.
2. Open the script and create parameters for username and password.
3. Fill in the values for the parameters in the flat file.
4. Change the values of paramters on every iteration.
5. Run the script for 10 iterations.
How to Parameterize a test script in Load Runner?
Select the text to be parameterized->R-click on that text you will have a option called Replace with parameter(click)->Here you will be creating a new parameter . In this you will have to the parameter name and when you click on properties, you will get one more pop up window in which you can create a table and add rows so that you give as parameters(values to be substituted when script is run) as you want.
Notice that when this process is finished your selected text will be replaced with the parameter name you gave and that will be in a pair of flower brackets & also in some different color.
Next time onwards in the same script, if you want to parameterize another text, when you right click you will be able to see the option 'Use Existing Parameter'. And you can include as many parameters as you want also you can paramterize with the same parameter.
To view the parameter substitution while replaying go to RunTime Settings->Log->Enable->Extented Log->Parameter Substitution
This is how you will be able to do regression testing using loadrunner.
Tuesday, July 22, 2008
Why We need Test Automation?
Hello,
Today I was working on QTP and the developer next to my cube came to me and asked what is this? I said I am doing Test Automation. He was surprised to see how QTP automates complex Test Cases. He said if this software does everything? I said YES it does everything what you teach it. Functionality Testing tools do what we teach them. They will repeat test scripts number of times we want them to do. Whenever we get an application to test, first we start with digging out Test Scenarios and writing Test Cases. Once we get an application, we will execute the test cases we written. First time execution of Test Cases is always Manual Process. We cannot automate the Test Cases before the Build or Application is stable. Automation is mainly useful for Regression Testing. When first round of Manual Testing is completed and we come up with number of bugs. When development team fixes those bugs, we must re run the entire test cases to make sure that modification of code in one part(module) of application has not produced any ill effects on other parts of an application(Regression Testing). For this Manual Testing will take lot of time and it will be boring exercise for Testers. If we automate set of Test Cases for Regression testing, it will be easy for us to run them whenever some modification or debugging is done in some part of application.
I found QTP as best tool available for Functionality Testing, One can download this tool from HP's site and learn it within 14 days. I found QTP help and tutorial more than enough for self learning. Also, you can always google for your doubts. One can allocate dedicated time for learning and learn this tool very easily. You will find the tutorial section explained everything with the examples(there are demo applications with this trial versions). Try to write and execute test caes for the demo application provided with the trial version. One who knows VB script can easily learn enhancing and modification of Test Scripts.
Main points to learn in QTP:
1. Understand using of different checkpoints.
2. Parameterizing values(Test Inputs).
3. Using Regular Expressions.
4. Working with multiple Actions.
5. Analyzing Test Results.
I hope now we can start learning QTP, and you can post your questions and doubts as comments to this post. Experts can answer them.
Today I was working on QTP and the developer next to my cube came to me and asked what is this? I said I am doing Test Automation. He was surprised to see how QTP automates complex Test Cases. He said if this software does everything? I said YES it does everything what you teach it. Functionality Testing tools do what we teach them. They will repeat test scripts number of times we want them to do. Whenever we get an application to test, first we start with digging out Test Scenarios and writing Test Cases. Once we get an application, we will execute the test cases we written. First time execution of Test Cases is always Manual Process. We cannot automate the Test Cases before the Build or Application is stable. Automation is mainly useful for Regression Testing. When first round of Manual Testing is completed and we come up with number of bugs. When development team fixes those bugs, we must re run the entire test cases to make sure that modification of code in one part(module) of application has not produced any ill effects on other parts of an application(Regression Testing). For this Manual Testing will take lot of time and it will be boring exercise for Testers. If we automate set of Test Cases for Regression testing, it will be easy for us to run them whenever some modification or debugging is done in some part of application.
I found QTP as best tool available for Functionality Testing, One can download this tool from HP's site and learn it within 14 days. I found QTP help and tutorial more than enough for self learning. Also, you can always google for your doubts. One can allocate dedicated time for learning and learn this tool very easily. You will find the tutorial section explained everything with the examples(there are demo applications with this trial versions). Try to write and execute test caes for the demo application provided with the trial version. One who knows VB script can easily learn enhancing and modification of Test Scripts.
Main points to learn in QTP:
1. Understand using of different checkpoints.
2. Parameterizing values(Test Inputs).
3. Using Regular Expressions.
4. Working with multiple Actions.
5. Analyzing Test Results.
I hope now we can start learning QTP, and you can post your questions and doubts as comments to this post. Experts can answer them.
Subscribe to:
Posts (Atom)
