To resolve the TimeoutException and successfully use automationId in XPath, follow these steps:
Key Issues Identified:
- Hierarchy/Context Issues: The element exists in a container (e.g.,
Pane, Window) not referenced in XPath.
- Element Not Interactable: The element is present but not enabled/visible when the script runs.
- Static Delays Insufficient: Delays alone won’t address dynamic UI loading; explicit waits are required.
Step 1: Verify Full Element Hierarchy
Use Inspect.exe to confirm the element’s parent-child relationship.
Example Structure:
Window (Parent)
→ Pane[@Name="LoginPanel"]
→ Edit[@automationId="txtPassword"] // Target element
Step 2: Refine XPath with Parent Context
If nested, include parent containers to avoid ambiguity:
//Pane[@Name='LoginPanel']//*[@automationId='txtPassword']
//Window//Edit[@automationId='txtPassword'] // Explicit control type (`Edit`)
Step 3: Create a Robust Test Object
Avoid raw XPath in scripts; define a test object in the repository:
- Object Repository → New → Windows Test Object.
- Add Property:
- Name:
automationId (lowercase “i”)
- Value:
txtPassword
- No need for XPath!
Step 4: Script with Explicit Waits and Focus
import com.kms.katalon.core.windows.keyword.WindowsBuiltinKeywords as Windows
// Wait for parent window first (critical!)
Windows.waitForElementPresent(findWindowsObject("LoginWindow"), 30)
// Optional: Focus parent container
Windows.focus(findWindowsObject("LoginWindow"))
// Wait for password field to be interactable (not just present!)
Windows.waitForElementClickable(findWindowsObject("PasswordField"), 30)
// Set text using the test object
Windows.setText(findWindowsObject("PasswordField"), "your_password")
Step 5: Advanced Troubleshooting
If the error persists:
A. Check if the Element is Enabled
def element = Windows.findElement(findWindowsObject("PasswordField"))
assert Windows.elementEnabled(element) == true
B. Use Absolute XPath Temporarily
Extract the full path from Inspect.exe (e.g., for debugging):
//Window[@Name='Login']/Pane[@automationId='mainPanel']/Edit[@automationId='txtPassword']
C. RuntimeId Fallback
If automationId is unreliable (e.g., dynamic), use runtimeId from Inspect.exe:
//*[@runtimeId='42.12345.4.1']
Why This Happens:
- TimeoutException: The element exists but is in a container not yet loaded or focused.
- XPath Flakiness: Parent containers may change dynamically, breaking generic XPaths like
//*[@automationId=...].
Validation Checklist
| Scenario |
Solution |
| XPath works in Inspect.exe |
Use parent-child hierarchy in XPath. |
| Element not interactable |
Use waitForElementClickable(), not waitForElementPresent(). |
| Delays not working |
Replace static delay() with explicit waits. |
Final Script Example
import com.kms.katalon.core.windows.keyword.WindowsBuiltinKeywords as Windows
// 1. Wait for parent window
Windows.waitForElementPresent(findWindowsObject("LoginWindow"), 30)
// 2. Focus parent container (critical for nested elements)
Windows.focus(findWindowsObject("LoginWindow"))
// 3. Wait for password field to be interactable
Windows.waitForElementClickable(findWindowsObject("PasswordField"), 30)
// 4. Set text
Windows.setText(findWindowsObject("PasswordField"), "your_password")
Define automationId in test objects, focus parent containers, and prioritize waitForElementClickable() over static delays. If issues persist, share a screenshot of the element hierarchy from Inspect.exe
