在开启QTP之前运行的程序能被成功识别的特例

The SIEBEL add-in uses SIEBEL Automation API, so if a SIEBEL application is
launched before QTP, QTP will still be able to identify the Siebel objects. This is
because even though Siebel runs inside a web Browser, QTP will not identify the
Browser properly but rather identify it as a normal native window.

Any Windows application that uses just native Windows objects (Window,
Dialog, WinEdit etc.) can be launched before QTP itself. QTP uses native system
APIs (Let FindWindow, FindWindowEx etc.) to identify these objects and is
therefore not dependent on the prior launching of QTP. Java applications also
can be identified even if the application is launched before QTP. QTP uses three
Windows environment variables (_JAVA_OPTIONS, IBM_JAVA_OPTIONS and
JAVA_TOOLS_OPTIONS) to inject its JVM hook and the application is hooked
irrespective of whether QTP is launched or not.

The SAP add-in uses SAP Scripting GUI and therefore a SAP GUI application will
still be identified correctly even if launched before QTP.