| || |
I have posted a question about QTP's capability of recognizing the Terminal Server Screen but got no respond so far, is there a way to make QTP recognize the Terminal Server's Screen by Terminal Emulator Add-in or some thing else? I really need to know the answer.so, friends, Please help me.
[ 05-09-2005, 08:09 AM: Message edited by: Pablo Ahsan ]
Have you tried posting your question in the QTP forum?
Product-specific questions usually get the best response in their own forum, rather than here in this more general forum.
Terminal Server: is Windows Terminal Server which acts like a mainframe, in the sense that a server (say, like mainframe) will be at one location with one or many applications on it. This is accessed by many people directly (like people used to access main frame thru dumb terminals) thru RDP (remote desktop) or web-browser so that they will be directly on the server itself rather than browser acting as a client.
You might ask why people have to use it. For example, your applications are hosted on a powerful server. But the users are in London. If they access the applicaton thru normal web (like a web-based application) they can only access it thru the available bandwidth (say only 56k), then they will be limited by the bandwidth.
On the other hand, if the application is hosted on a Terminal Server, then the connection they will be directly transported to the Terminal server itself.
The screen they will be seeing is Terminal server itself rather than a browser client. They can run the application as if they are sitting before the Terminal Server itself.
You might ask why to test this? Because windows terminal server can not provide unlimited number of connections. Generally companies want to test how many connections the terminal server simultaneously can withstand and how the app behaves in such situations.
This is my understanding, though I have not tested them.
The second question Terminal Emulator is different.
What happens during a funtinal automated testing?
A software tool (e.g QTP /winrunner) comes with specific APIs of some popular client interfaces( like VB, Browser (web) etc., Because these API's allow the tool to recognize the objects of the during recording.
These are called add-ins. Okay, what should one do if a mainframe application accessed thru Terminal Emulator, or a UNIX application accessed from windows thru Telnet How do we record them? A third party tool (I think
powerterm) was added to Winrunner (when I was working with it). So when you select Terminal Emulator & start recording a Telnet session, it helps. But not a Terminal Server session. Both are different altogether.