QTP Question 03: Explain QTP Testing process?
The QuickTest testing process consists of 7 main phases:
Create your test plan
Prior to automating there should be a detailed description of the test including the exact steps to follow, data to be input, and all items to be verified by the test. The verification information should include both data validations and existence or state verifications of objects in the application.
Recording a session on your application
As you navigate through your application, QuickTest graphically displays each step you perform in the form of a collapsible icon-based test tree. A step is any user action that causes or makes a change in your site, such as clicking a link or image, or entering data in a form.
Enhancing your test
Inserting checkpoints into your test lets you search for a specific value of a page, object or text string, which helps you identify whether or not your application is functioning correctly.
NOTE: Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier and faster to add the checkpoints during the recording process.
Broadening the scope of your test by replacing fixed values with parameters lets you check how your application performs the same operations with multiple sets of data.
Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.
Debugging your test
If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.
Running your test on a new version of your application
You run a test to check the behavior of your application. While running, QuickTest connects to your application and performs each step in your test.
Analyzing the test results
You examine the test results to pinpoint defects in your application.
Reporting defects
As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.
Create your test plan
Prior to automating there should be a detailed description of the test including the exact steps to follow, data to be input, and all items to be verified by the test. The verification information should include both data validations and existence or state verifications of objects in the application.
Recording a session on your application
As you navigate through your application, QuickTest graphically displays each step you perform in the form of a collapsible icon-based test tree. A step is any user action that causes or makes a change in your site, such as clicking a link or image, or entering data in a form.
Enhancing your test
Inserting checkpoints into your test lets you search for a specific value of a page, object or text string, which helps you identify whether or not your application is functioning correctly.
NOTE: Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier and faster to add the checkpoints during the recording process.
Broadening the scope of your test by replacing fixed values with parameters lets you check how your application performs the same operations with multiple sets of data.
Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.
Debugging your test
If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.
Running your test on a new version of your application
You run a test to check the behavior of your application. While running, QuickTest connects to your application and performs each step in your test.
Analyzing the test results
You examine the test results to pinpoint defects in your application.
Reporting defects
As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.
posted by QTPro at
2:26 AM
6 Comments:
Does IDE provide feature to add different types of checkpoints? (text, image, database)
By
Unknown, at 2:02 AM
We are a Microsoft shop using QuickTest Pro 9.0 (QTP) w/ .NET for our functional testing. I’ve been asked to somehow map the QTP Test Results back to the Requirements for Traceability to determine our test coverage. While I mentioned TestDirector/Quality Center and how wonderful that was with its seamless interface, Requirements Management, Lab, Test Planning, Defect Management, etc., and spectacular reporting…it was a brief conversation because all of our requirements are already being managed in Microsoft Team Foundation Server (TFS).
My question is: What are my options for determining Functional Test Coverage between QTP and TFS? Can it be done at some level? If so, how and how difficult is it to do?
By
Unknown, at 2:06 PM
when run QTP 9.0 display error visual studio just-in-time debugger.
"...occurred in QTPro.exe [1856]. Just-In-Time debugging...". this error is sometime displayed. So how can I remove it?
By
Unknown, at 1:58 AM
Can we use QTP with MAGIC software.
By
shailendra, at 8:24 AM
I did installed QTP 9.2 and 9.5 and in both version, at the time I want to open a browser, Visual Studio JIT Debugger window will open that prevent opening any browser unless you uncheck the activeX button which will results in errors when running the recoded test
By
Unknown, at 2:51 PM
I have the same question..What are my options for determining Functional Test Coverage between QTP and TFS? Can it be done at some level? If so, how and how difficult is it to do?
By
Unknown, at 9:52 AM
Post a Comment
<< Home