Forum Discussion
UI Path and TestComplete I know use some similar technology for identifying components so there's no surprised they have similar difficulties (BTW, I'm using UI Path 2019.10.4 these days so... hiya!).
HOWEVER... as noted in this thread, TestComplete currently is well documented as not supporting PB 2019 as that's a newer version than the 12.6 that is documented. In order for TestComplete to support PB 2019, that is work for the SmartBear folks to build that support into the tool. There's no work around or what not for it other than sending general keystrokes to the screen, using OCR technology or image recognition technology.
Being a UI Path user myself I know that you can do the same there. You might want to consider using ComputerVision, some sort of OCR identification, or image identification with anchors to find your objects in the short term. I'd be willing to bet that, if TC is having issues with PB 2019, then the same would hold true for UI Path that he UI Path folks will need to make code changes to support the new version of PowerBuilder.
I also made contact with Appeon tech support and they said that they changed something regarding MSAA 2.0 in DW with PB2019.
Also, keep in mind that Accessability Insights, Microsoft's tool for checking MSAA implementation, don't work with PB2019 either. So we have 3 tools, which worked with 2017, but stoped working with PB2019. Coincidence? :)
Related Content
Recent Discussions
- 4 hours agoSvetaG