0

Inspect.exe is behaving differently on different machines my development pc can see all the automationIds I expose in my application. But on our testers PC Inspect cant find these automationIds. Both PC are using the same windows sdk inspect application. I saw this article describing how QT runtime could be a cause. But there is no description of how the QT runtime issue was resolved between the 2 pcs.

user3094988
  • 51
  • 1
  • 3
  • 2
    What is `inspect.exe`? – RedX Feb 07 '19 at 11:54
  • What does QT have to do with C# and what is `inspect.exe`? What you call automation IDs are most likely the *Class IDs* and *Prog IDs* of COM and automation objects. You can find them in the registry. They aren't related to UI or testing. – Panagiotis Kanavos Feb 07 '19 at 11:56
  • 1
    I looking for help with UI automation using PyWinAuto to test WPF applications UI. Inspect.exe is part of the windows 10 SDK, AutomationIds are an attached properties used to label controls. https://msdn.microsoft.com/en-gb/windows.ui.xaml.automation.automationproperties.automationid – user3094988 Feb 08 '19 at 15:39
  • @RedX @Panagiotis Kanavos guys `Inspect.exe` is GUI inspector tool from Windows SDK. Tags "ui-automation" and "wpf" assume you know what it is. – Vasily Ryabov Feb 09 '19 at 16:54
  • @user3094988 maybe it's worth taking a look at how you build your app. The tag is "WPF" so the app doesn't contain any Qt element inside, right? Please describe the app structure in more details. Screenshots from `Inspect.exe` would be helpful. – Vasily Ryabov Feb 09 '19 at 16:58
  • It might be different versions of .NET Framework since it's probably not a Qt. – Vasily Ryabov Feb 10 '19 at 22:01
  • I have added a AutomationIds to a syncfusion datagrid xmlns:sf="schemas.syncfusion.com/wpf" – user3094988 Feb 11 '19 at 10:51

0 Answers0