I have a webpage. When I click on the Home button I get the list of various clients. And when I click one of the client it takes to a to asp page with the complete client info. In QTP can I some how automate this process of retrieving the final client info? Any ideas..
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
QTP webpage retrieval
- Thread starter saibsk
- Start date
You might want to try recording the process up to the asp page.
Once there, use QTP to collect the info directly from the page and chuck it in a variable. Then parse it as necessary to make use of it as you need.
Cheers,
Dave
"Yes, I'll stop finding bugs in the software - as soon as you stop writing bugs into the software." <-- Me
For all your testing needs: Forum1393
Once there, use QTP to collect the info directly from the page and chuck it in a variable. Then parse it as necessary to make use of it as you need.
Cheers,
Dave
"Yes, I'll stop finding bugs in the software - as soon as you stop writing bugs into the software." <-- Me
For all your testing needs: Forum1393
- Thread starter
- #3
Why do you need to change the script?
The script is the process remember - your process hasn't changed.
You get to the final screen and collect the client details.
What happens with them at this point - are they verified, or written out elsewhere?
If you want to collect all the client details and do something with the entire lot of them, then put the whole process inside a loop and use an array to store each individual client's details.
If you can provide more information about what you're trying to do, I can help more.
Cheers,
Dave
"Yes, I'll stop finding bugs in the software - as soon as you stop writing bugs into the software." <-- Me
For all your testing needs: Forum1393
The script is the process remember - your process hasn't changed.
You get to the final screen and collect the client details.
What happens with them at this point - are they verified, or written out elsewhere?
If you want to collect all the client details and do something with the entire lot of them, then put the whole process inside a loop and use an array to store each individual client's details.
If you can provide more information about what you're trying to do, I can help more.
Cheers,
Dave
"Yes, I'll stop finding bugs in the software - as soon as you stop writing bugs into the software." <-- Me
For all your testing needs: Forum1393
- Thread starter
- #5
But when the tester has to select the client from the list. He could click on any of the clients. Then from that webpage we would be taken to the page with the complete client info. And then I want process the client information. I don't want to collect all the clients info only the one he clicks on. But I wont know beforehand which client he is going to click. So I need to somehow automate the test between the list of clients and the corresponding client information.
The process you describe seems a bit pointless though. Why would you have a manual tester executing this process when it should all be automated?
You need to explain why this is being done with a manual tester, and why the test does not involve checking all the information?
Surely with the automation, it's trivial to cover your entire client base, rather than one or two that the manual tester selects. And if you want to retain the manual element, it's be simpler to make the whole test manual, than expect the QTP script to run patiently waiting in the background then jump in to grab the data you want.
Can you explain what you're doing and why? It may not be a test suited to automation.
Cheers,
Dave
"Yes, I'll stop finding bugs in the software - as soon as you stop writing bugs into the software." <-- Me
For all your testing needs: Forum1393
You need to explain why this is being done with a manual tester, and why the test does not involve checking all the information?
Surely with the automation, it's trivial to cover your entire client base, rather than one or two that the manual tester selects. And if you want to retain the manual element, it's be simpler to make the whole test manual, than expect the QTP script to run patiently waiting in the background then jump in to grab the data you want.
Can you explain what you're doing and why? It may not be a test suited to automation.
Cheers,
Dave
"Yes, I'll stop finding bugs in the software - as soon as you stop writing bugs into the software." <-- Me
For all your testing needs: Forum1393
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question