Recording a Declaration for a Browser Page Containing Many Child Objects

This functionality is supported only if you are using the Classic Agent.

When trying to record a declaration for a browser page containing many child objects, CPU usage stays at 100% and Silk Test Classic seems to lock up.

If you add the Partner.ini setting:

[Runtime]
AgentTimeout=<value in milliseconds>

and set it very large, for example 600000 (10 minutes), then eventually Silk Test Classic will return a declaration. The default is 240000 milliseconds (240 seconds or 4 min).

The setting must be put into Partner.ini, not into an option set.

For large pages, recording will be very slow, and the CPU will max out while the browser extension initially gathers the page information, and again when it transfers the information to the Agent. If you refrain from moving the mouse around and wait long enough, though, the system will eventually free up.