3 ms·
Article should really be called “our teams troubles writing automated UI tests for native windows apps”. The article mentions “If you follow the Page Object Mo
by jchb 7y ago
Article should really be called “our teams troubles writing automated UI tests for native windows apps”.
The article mentions “If you follow the Page Object Model pattern, then for each page and control in your application, you create models so your tests can find and interact with the elements on that page or control.“.
Not being a windows programmer I am not familiar with this model in detail, but a major issue seems to be that the UI toolkit doesn’t have any built in support for UI automation.
For example on iOS and macOS, the accessibility system (which is what e.g the screen reader for blind users use to drive the application) is repurposed for UI tests.
This means that if your app is accesible, which it pretty much is by default where you use standard UI controls, with minor code changes such as assigning unique identifiers to UI elements where needed, it is also UI-testable.
- _____s 7y agoThe Page Object pattern is common in Ruby (and some JS frameworks, like ember.js) too. I agree that the issues mentioned in this article seem mostly windows app centric. For JS apps running in the browser, the testing story is pretty good these days.
- pjmlp 7y agoWPF and UWP support UI Automation, there are even VS project templates for. Forms does not, beyond the typical Win32 SendMessage(). However there are good UI tooling that does a good job in spite of it, assuming that one is willing to pay for them. https://www.ibm.com/us-en/marketplace/rational-functional-tester https://www.ibm.com/us-en/marketplace/rational-functional-te... https://www.ranorex.com/ https://www.ranorex.com/ https://eggplant.io/ https://eggplant.io/ https://www.tricentis.com/ https://www.tricentis.com/ https://www.microfocus.com/en-us/products/unified-functional-automated-testing/overview https://www.microfocus.com/en-us/products/unified-functional...