Hi,
OLE VB scripting? Are they serious!? Do they mean using Microsoft Visual Basic to script OLE interfaces? Well, that's fine, if a) you know VB and b) the thing you want to automate has an OLE interface and c) you have the docs that describe that OLE interface and lots and lots of time. But if you're not a programmer, or want a tool that is more easily understood, faster to get up to speed with, and, more importantly, want to automate **ANYTHING**, including apps which do not expose OLE/ActiveX interfaces, then that isn't going to work. Macro Scheduler is.
QTP - I think you are referring to Quick Test Pro. That's a software testing tool. A different beast. It has built in features for testing. The only overlap is in the scripting language used by QTP. And that's why you'd want Macro Scheduler, because QTPs scripting language is not as rich. See what Gale said here:
http://www.mjtnet.com/automated_testing.htm
"We found the problem with object oriented test tools like WinRunner, QTP, SilkTest, etc is the partial or non-existant 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 Windows API command similar to Macro Scheduler's GetPixelColor function to find the images. It worked but was nowhere as well developed or convenient to use as Macro Scheduler's Image Recognition functions. If you have bitmaps of the images your application will display, you can write a script before the application is coded. Macro Scheduler and AppNavigator are great because the same solution works for all technologies that run on Windows. Because the solution is image based it works in development, independent test, and production environments."
Gale Dyvig, Seattle Children's Hospital
Some people have used trad test tools like QTP *with* Macro Scheduler to do the scripting part, or to augment the scripting where the tool's script language lets down. Now we have the SDK that can be done even more seamlessly. The SDK could also be used in the "OLE VB" solution to augment VB's capabilities more easily.
In short. Macro Scheduler can automate WAY more than VB or QTP and, it can do it more easily.
