UI Testing
UI Testing
- Subject: UI Testing
- From: Patrick Cusack <email@hidden>
- Date: Tue, 01 Apr 2014 15:39:10 -0700
I have been testing a non-cocoa based UI for the better part of two years. When I initially approached the project my thought was to try and perform automated tests using OSX accessibility hooks (the application was written in Qt). As the Qt libraries didn’t expose any accessibility information, I passed on it. I performed automation in a few areas where it was important. Otherwise I tested the application though general use. My only focus has been OSX and Windows. I didn’t have the challenge of testing web applications across multiple browsers and version of web-renderers.
Just recently, I discovered Frologic ( http://www.froglogic.com/squish/gui-testing/editions/mac.php ) which allows UI testing against native OSX applications (carbon and cocoa apps).
It appears that Frologic does some kind of code injection into the target binary to see and navigate through the application’s user interface.
The application says it can do the following:
“Test your Mac applications using the Squish for Mac edition. Squish for Mac works on all Mac OS X versions, including Intel and PowerPC. Offering support for standard and complex controls as well as script access to the Cocoa and Carbon APIs.”
I guess I am some what perplexed as I would love to know what strategies these programs use to examine an applications UI apart from standard traditional accessibility apis. Would any one have an idea or explanation?
Thanks,
Patrick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden