| || |
I am doing a little research on which Terminal Emulator to use for automation using WinRunner. I am using WinRunner 8.2 and I have the TE 7.6 add-in installed and that side is just fine. Now coming to the system I have to test, it’s developed using UNIX-SCO. We have VT220 terminal Emulation as default. Even if I use VT100 Terminal Emulation, I wouldn’t be able to use TE_* functions at all. All the Terminal Emulators that are enlisted in TE addin documentation do not work with the system I have to test. I do not want to go and do the screen captures for text as system changes very frequently and the screen content also changes.
So, I was searching this forum for some tips and I came across postings that tell that a client application PuTTY works fine with WinRunner. I want to know more about how WinRunner works (addins to be used, any patches, and any configurations on WinRunner side) with this application. Any suggestions are welcome. WinRunner + Terminal Emulator is a very new sector for me, so please excuse my terminology.
Please feel free to post me with any questions you may have as I know this may be confusing.
Re: Terminal Emulator
We are using the combination of Rumba 7.2.0(SP0) and Winrunner 8.0. We don't connect through the terminal emulator but directly through the EHLLAPI. For us this causes quite a few problems, we get unpredictable en not repeatable errors.
Some expert users also gave me the hint to use PuTTY so I would go with that.
Re: Terminal Emulator
As in my previous posting I was searching for a good Terminal Emulator that works with WinRunner. Well there are lots of dependencies for this. As given in the TE addin users guide WinRunner TE 7.6 addin supports only 3270 and 5450 emulations completely and VT100 partly for quite a few terminal emulators. The other Terminal Emulators that are not supported by TE addin goes into Other VT100 category. This has different configuration method than the the others.
I had to use VT100 because the application I am testing is an Unix-SCO based application. I can only use VT100 or VT220 emulation styles.
When I was using Other VT100 option in TE 7.6 addin and trying to use TE_get_text function, I was getting weird results.
I searched in Mercury support and found this wonderful tool WinGrid3.exe as a solution for this problem. The problem with TE_get_text before was that WinRunner divides the Terminal Emulator screen in to 80 Col X 24 Rows grids. These grids are not properly alligned with Terminal emulator. To put it simple, The Terminal Emulator you might be using might not be of same size as WinRunner is expecting it to be. So We Run this WinGrid3.exe on Terminal Emulator and resize our Terminal Emulator that the characters on Terminal emulator are well inside the grid of WinGrid and save the terminal emulator session.
The Knowledge base article number in MI support website is KBA # 1733.