WPF CLR应用UI测试报错：无法通过指定参数定位页面元素

Let's break down why you're hitting this error and fix it step by step:

First, Fix the Broken Catch Block Logic #

Your current TestInit method has a critical flaw: when the initial attempt to find ExitButton fails, you immediately try to find and click the same ExitButton again in the catch block. That's guaranteed to throw the same error! Your comment mentions clicking a "cancel button" for nested pages—let's adjust that logic to target the correct element first:

public virtual void TestInit()
{
    WindowsElement alarmButtonElement = null;
    WebDriverWait wait = new WebDriverWait(session, TimeSpan.FromSeconds(5));
    
    try
    {
        // Try to find ExitButton with an explicit wait
        alarmButtonElement = wait.Until(driver => driver.FindElementByAccessibilityId("ExitButton"));
    }
    catch (WebDriverTimeoutException)
    {
        // If ExitButton isn't found, look for the Cancel button (adjust AccessibilityId if needed)
        try
        {
            var cancelButton = wait.Until(driver => driver.FindElementByAccessibilityId("CancelButton"));
            cancelButton.Click();
            // Wait for the main page to load, then retry ExitButton
            alarmButtonElement = wait.Until(driver => driver.FindElementByAccessibilityId("ExitButton"));
        }
        catch (WebDriverTimeoutException)
        {
            throw new InvalidOperationException("Could not locate ExitButton or CancelButton on the page");
        }
    }

    // Verify the element exists and is displayed
    Assert.IsNotNull(alarmButtonElement);
    Assert.IsTrue(alarmButtonElement.Displayed);
}

Verify the Element's AccessibilityId is Correct #

The #1 cause of this error is using the wrong AccessibilityId (called AutomationId in WPF). To confirm the correct value:

• Open the Inspect Tool (included with the Windows SDK, or downloadable from Microsoft's toolset)
• Launch your WPF app
• Hover over the Exit button with Inspect and check the AutomationId property—this is the exact value you need to pass to FindElementByAccessibilityId
• Note: WPF controls don't auto-set AutomationId from x:Name; you must explicitly add AutomationProperties.AutomationId="ExitButton" to your XAML element for it to be detectable.

Replace Implicit Wait with Reliable Explicit Waits #

Your 1.5-second implicit wait might not be enough for your app to load elements. Explicit waits (using WebDriverWait) are more precise because they wait for a specific condition (like element visibility) instead of a fixed time. Update your tests to use these instead of relying solely on implicit waits or Thread.Sleep.

Check App Launch Configuration #

Double-check these details in your Setup method:

• Ensure the AlarmClockAppId path is correct (you have misSoloution—is that a typo for misSolution? Even a small typo here could cause unexpected behavior)
• Confirm appWorkingDir points to the correct directory where your app's dependencies live—an incorrect path might lead to the app loading in an unexpected state
• Try removing appWorkingDir temporarily if your app doesn't require a specific working directory to rule out context issues

Ensure You're Targeting the Correct Window #

Sometimes WPF apps spawn auxiliary windows (like splash screens) that take focus. Add code to switch to the main window after launch:

// In your Setup method, right after creating the session
// Give the app time to fully launch
Thread.Sleep(TimeSpan.FromSeconds(2));
// Switch to the main window (adjust the title check to match your app)
var windowHandles = session.WindowHandles;
foreach (var handle in windowHandles)
{
    session.SwitchTo().Window(handle);
    if (session.Title.Contains("Your App's Main Window Title"))
    {
        break;
    }
}

Final Quick Checks #

• Make sure Windows Application Driver is running as administrator (required to interact with desktop apps)
• Ensure your WPF app isn't running in elevated mode if the driver isn't—mismatched privileges can block element detection

内容的提问来源于stack exchange，提问作者Mohammad reza Kashi