Debugging the proxy code

Debugging the proxy code is an essential part of the proxy development process for problem determination. The proxy code containing the JAR file or .Net assembly file with the .dll extension is loaded into the application under test (AUT) process. To debug the proxy code, attach the respective debugger to the AUT process after the proxy binary files are loaded into the AUT.

Preparing the debug environment

About this task

Before you debug the proxy code, perform the following tasks:

Procedure

  • Save the debug version of the proxy binary files in the customization directory and restart HCL OneTest UI.
  • In case of Java, enable the JRE that the AUT uses with the HCL OneTest UI enabler.
  • In case of .Net, start the .Net AUT and record a click action on any control using HCL OneTest UI to enable it for testing.
    Note: The proxy assembly .dll file is loaded only when the first click is recorded on Windows and .Net applications. Windows and .Net applications are enabled dynamically for testing. In case of Java, the Application Configurator Tool enables the AUT.

Setting invocation timeout

Debugging proxies is time sensitive and the invocation times out after two minutes by default. To adjust timeout for debugging, add a DWORD value InvocationTimeout in milliseconds under HKEY_LOCAL_MACHINE\SOFTWARE\HCL Technologies\HCL OneTest UI in the Windows registry. A timeout during debugging throws a SpyMemory MutexTimeout exception.

Debugging record

The getChildAtPoint() method is the entry point for proxy debugging for record. Any user action calls the processMouseEvent() method, even before AUT sees the event. HCL OneTest UI processes the user actions, for example whether the action is a click or drag and accordingly the method specification and arguments are generated. For best results, use these methods to start inserting breakpoints.

Debugging playback

The getMappableChildren() method is the entry point for proxy debugging for playback. During proxy development, most ObjectNotFound problems that occur result from a mismatch between the object hierarchy that the record produces and the hierarchy produced during playback. Make sure that the getMappableParent() and getMappableChildren() methods are symmetrical.
Feedback