A couple of great posts in the new Software Testing forum are demonstrating the power of Macro Scheduler for automated testing.
Antonius Momac says in this post:
I’ve looked at more than 8 other automation tools. Some were from the big companies with many products like IBM (rational), HP/Mercury, and other more focused shops like Automated QA, Tethy Solutions, Redstone (eggplant) ….. However, the application I was putting under test was very particular. In fact, plain and simple, Macro Scheduler was the only tool that worked.
In this post Gale Dyvig said:
We found the problem with object orientated test tools like WinRunner, QTP, SilkTest, etc is the partial or nonexistant support for the objects under test. As new technologies are created the problem gets worse.
These tools have image based workarounds, but they need the script to specify the image location on the screen. We tried some workarounds based on a WINAPI command similar to GetPixelColor to find the images. It worked but was nowhere as well developed or convenient to use as Macro Scheduler’s FindImagePos. If you have bmp’s the images your application will display, you can write a script before the application is coded.
Macro Scheduler and AppNav are great because the same solution works for all technologies runnable on Windows. Because the solution is image based it works in development, independent test, and production environments.
Are you using Macro Scheduler for automated software testing? If so please post an introduction in the Software Testing forum. I’d love to know more about how people are using Macro Scheduler in automated software testing scenarios.
