Fixing 'Object Not Found' Errors in TestComplete for Scalable UI Automation

Details: Category: Testing Frameworks; By Mindful Chase; 23.Jul; Hits: 9

TestComplete is a commercial, GUI-based functional testing tool known for its robust support of desktop, web, and mobile automation. However, teams working in large enterprise environments often encounter sporadic failures or skipped tests—especially when executing suites via CI/CD pipelines or remote agents. One of the most challenging issues is the "Test Objects Not Found" error, which can arise intermittently despite visible and stable UI elements. This issue undermines test reliability and confidence, and is often rooted in synchronization gaps, dynamic object properties, or poor environment configuration. In this article, we explore the root causes of this issue, how it behaves across architectures, and best practices to stabilize object recognition in TestComplete-based test suites.

Mindful Chase

Writing Code, Writing Stories

tbd

Experience

tbd

More to Explore

Root Problem: Intermittent "Object Not Found" Errors in TestComplete

Background

TestComplete uses a name mapping engine and intelligent object recognition to interact with UI elements. In unstable environments or large-scale test suites, it may fail to locate controls even when they are rendered correctly. This creates false negatives and significantly erodes the trustworthiness of automated tests.

Architectural Triggers

The issue is more pronounced in the following contexts:

Remote agents running tests on virtual desktops or Citrix/VDI environments.
Applications with delayed rendering or late-binding UI frameworks (e.g., WPF, Electron, Angular).
UI elements with dynamic IDs, class names, or index-based hierarchies.
Overloaded test runners without proper waits or synchronization mechanisms.

Diagnostics and Symptom Analysis

Step 1: Review Name Mapping Hierarchy

Open the Name Mapping editor and verify if the object properties being used (like `WndClass`, `ObjectType`, `Index`) are static or prone to change. Use wildcards or conditional properties as needed.

Step 2: Enable Extended Logging

Use TestComplete's built-in logging and set `Log.Options.TraceLevel = 3` to capture detailed object recognition steps.

Log.Message("Attempting to access UI element", LogAttributes.Trace);

Step 3: Use Object Spy

While the test is paused, use the Object Spy to manually identify the problematic object and compare it against the Name Mapping entry.

Step 4: Validate Test Execution Environment

Ensure screen resolution, DPI scaling, and OS language settings match between local and remote machines. UI coordinates and object positions may shift due to these factors.

Fixes and Stabilization Techniques

1. Use Property Sets with Wildcards

Instead of relying on strict identifiers, use a combination of stable properties with wildcards for dynamic attributes.

<ObjectType=Window>
<WndCaption=*'Login'*>
<Index=1>

2. Add Smart Waits or Explicit Timeouts

Enable Smart Waits globally or insert `WaitAliasChild` and `WaitWindow` functions with adequate timeouts.

Aliases.App.MainWindow.WaitAliasChild("SubmitButton", 10000);

3. Synchronize with Application State

Use custom checkpoints that wait for an expected property (e.g., visibility or enabled state) before proceeding.

while (!Aliases.App.LoginButton.Enabled)
  Delay(500);

4. Modularize and Isolate Tests

Break down large keyword tests into smaller, reusable blocks to better control state and reduce complexity.

5. Align Test and Execution Environments

Standardize screen resolution, scaling (e.g., 100% DPI), and OS settings across all test execution agents.

Best Practices for Enterprise Stability

Use Tagged Objects for components that change often and avoid hardcoding indices.
In CI environments, disable screen savers, lock screens, and energy-saving modes to keep the UI accessible.
Leverage TestComplete's Execution Plan dependencies to control test order and avoid premature interactions.
Regularly update Name Mapping files to reflect evolving UI structures.
Conduct nightly validation runs to flag broken object mappings proactively.

Conclusion

TestComplete's rich UI automation capabilities are powerful, but they demand disciplined setup and maintenance to avoid flakiness—particularly around object recognition. By auditing Name Mappings, introducing smart synchronization, and aligning environments, teams can drastically reduce false negatives and stabilize their UI automation pipelines. A consistent, modular, and observation-driven testing approach is essential for scaling TestComplete in large organizations.

FAQs

1. Why does TestComplete sometimes fail to find UI elements on remote machines?

This is often due to screen resolution mismatches, missing UI focus, or differences in rendering between local and remote environments.

2. Can dynamic objects be tested reliably in TestComplete?

Yes, by using wildcards or conditional properties in Name Mapping, you can stabilize test cases even when element IDs or captions change frequently.

3. What is the impact of Smart Waits?

Smart Waits improve stability by waiting for objects to become available before throwing errors, reducing the need for hardcoded delays.

4. How do I debug "Object Not Found" issues quickly?

Pause test execution and use the Object Spy to inspect live UI state, then compare with mapped properties and logs for discrepancies.

5. Is TestComplete suitable for CI/CD automation?

Yes, but it requires careful setup—consistent environments, synchronized test data, and robust object identification strategies to ensure success.

Contact Us