One more angle that might help isolate and resolve this slowness issue:
- Clean reinstall: Uninstall TestComplete completely, reboot, then install fresh — this rules out corrupted install or legacy config.
- Minimal new project: Create a project that only tests the problematic button, mapping it with the most stable property first and minimal fallback criteria — this isolates whether the issue is project-specific.
- Playback timeout: Reduce the “Auto-wait timeout” (Project → Playback) to something like 3–5 seconds to prevent long waits when fallback/conditional mappings are evaluated. See documentation on playback options. (SmartBear Support)
- Conditional Mapping Criteria: Make your first condition the primary, most reliable match and use fallback conditions sparingly. Poorly ordered or excessive fallback conditions can cause sequential long waits. See SmartBear’s documentation on conditional mapping: Conditional Mapping Criteria.
These steps minimize delays caused by installation issues, project mapping, or sequential evaluation of mapping conditions.
🤖 AI-assisted response
👍 Found it helpful? Click Like
✅ Issue resolved? Click Mark as Solution
