I am testing our character mode D3 application (an accounting package)
by having an automated test tool send keystrokes to Wintegrate,
capturing the screens, and comparing them.

Would like to hear from anyone else doing something similar.

Our app is normally run by customers thru Wintegrate or another
terminal emulator.

The test tool is called TestComplete from AutomatedQA.com. It is
usually used for testing GUI or Web apps. It is scripted in Javascript,
VBscript, or several other languages. Other similar tools are Rational
Functional Test and Mercury QuickTest (though they are more expensive
and presumably more powerful).

The tool just thinks it is testing Wintegrate, a win32 app on the same
PC.

The main challenges I faced have been
- slow speed of sending control keys to Wintegrate to activate menu bar

- solved by using OLE interface of Wintegrate to capture screen (as
text)
- in character mode app, error messages appear various places on the
screen, hard to automatically spot
- filtering out lots of unimportant messages and differences from the
real errors
- am using a lot of Javascript Regexp's to do this

Hi, not quite the same thing, but in about 1998 i embedded a
wintegrate session in a browser app. The wintegarte session connected
to the UK Viewdata network (videotext system) to connect to tour
operators and book holidays. My App was in redback and was a travel
agency system. The browser scripted wintegarte to login, enter trip
details (from, to, when, passenger etc) and to then capture the booking
screens that contained refrenece, price breakdown etc.

All this was done by javascript, wintegrate as an activex object, and
the wintegrate script commands, it worked very well. So i certainly
think what you are doing is possible using these methods.

rgds
Symeon.

tom t la ca wrote:
I forgot another big challenge, which is the the test tool
(TestComplete) sends keys to windows based on their window class, and
the window class differs from PC to PC and from run to run. for
instance the class of the main screen window was

"Afx:1000000:b:10011:0:0"
"Afx:1040000:b:10011:0:0"
"Afx:1050000:b:10011:0:0"

at different times.

I was able recently to list the values of OLE symbols with the Visual
Basic Editor built into MS Word (2003):

· do Tools, Macros, Visual Basic Editor.
· Then in the editor do Tools, References, Browse which opens Add
Reference, then change the file type it looked for to .ocx (default is
..dll).
· open \Program Files\Wintegrate 5\wSession.ocx
· do View, Object Browser - opens panes on right with list of all
symbols
· change pulldown at top of symbol list from <All Libraries> to
WSESSIONLib
· now lists just Wintegrate symbols