January 4, 2006

Macro Scheduler 8.0 Released

Filed under: Announcements, Macro Recorder — Tags: — Marcus Tettmar @ 1:53 pm

The eagerly awaited new version of Macro Scheduler, version 8.0, was released this morning. We’ve added some really cool new features which allow macros to be scheduled even when Windows is logged out and automatically log back into Windows (or unlock the workstation) when needed. AutoLogon will automatically log into Windows, run the macro and then log out again. This means macros which require full access to the GUI, network resources, and user-level access rights can be scheduled to run even when Windows has been logged out or locked. We’ve also added new commands to get list box elements and tree nodes and improved existing script functions. The Macro Recorder has been improved, more debug functions have been added and we’ve added Unicode support so that double-byte characters can be sent to other applications … plus lots of other improvements. More info: Macro Scheduler 8.0
Thanks to everyone who helped beta test this major new release!

January 3, 2006

Image Recognition

Filed under: Scripting — Tags: — Marcus Tettmar @ 4:43 pm

When we are automating Windows applications we nearly always need to be able to detect new windows and wait for windows to open and close and be ready etc.  Unfortunately there are times when this is not possible.  Flash applications for example are just exposed as graphics and expose no windowed controls that we can grab a hold of.  Java applets are also a bit tricky as they use internal objects which Windows doesn’t know about.  Another tricky scenario is trying to automate Terminal Server or Citrix sessions at the client level.  The client just gets a graphical representation of the server’s screen.  There is no access to the objects that make up the user interface within the session unless you are on the server itself.  So we used to have to install Macro Scheduler on the server if we wanted to automate applications inside the session.  This is fine if we have access to install stuff on the server.  There are times when we don’t.

Another issue that came up recently was a customer that wanted to test the network lag time between a user entering some data into a Windows Terminal Server client and the server serving up the following page.  The conundrum is that if you install Macro scheduler on the server and make it wait for a new window there is no lag time since all the automation is happening locally to the server.  But on the client there is no way to know about the new window object.  Until now.

Enter the Macro Scheduler Image Recognition Library.   This includes functions that compare images and find images within larger images.  In other words we can compare screens and find objects within screens by searching for their image.   We can find and click on buttons and other controls and wait for the screen or parts of the screen to change based on what they look like.  This lets us automate applications graphically rather than having to know about windows and GUI controls.  In fact this is more analogous to how a user uses a computer.  The user watches the screen for changes in appearance and finds objects by looking at them with his eyes.  He looks at what he sees.  He doesn’t worry about window handles, x and y coordinates.  So the Image Recognition Library means we can automate any application regardless of the technology it uses to expose it’s interface.  It works at the graphical level of the screen.  You can download the Image Recognition Library at http://www.mjtnet.com/imagerecognition.htm

Note: Image Recognition is now native within Macro Scheduler and the separate library is no longer required.

December 30, 2005

Internet Macros

Filed under: General — Tags: — Marcus Tettmar @ 11:03 am

Ever since Macro Scheduler has supported VBScript it has been possible to control Internet Explorer directly via it’s ActiveX interface. Here are some examples:

http://www.mjtnet.com/usergroup/viewtopic.php?t=1511
http://www.mjtnet.com/usergroup/viewtopic.php?t=1461

However, this approach requires a fair amount of coding and, for complex IE scripting, a good understanding of the Document Object Model. That’s why we developed WebRecorder. WebRecorder is like a tabbed browser. As you surf WebRecorder watches what you click on and monitors form field entries and builds a script as you go. When you’re done you simply run the script in Macro Scheduler and the activity is played back. WebRecorder cuts out any need for coding and also copes better with nested frames where VBScript fails due to site scripting security limitations.

Macro Scheduler has supported VBScript, and therefore the ability to automate IE and do things like wait for pages to finish loading, and click on tags etc, since 1998. WebRecorder was introduced in 2004. As much as I hate to admit it there are other products out there that do similar things. So imagine how shocked I was the other day when I stumbled across a website for another macro product that claimed it had unique internet functionality that no other software had. It claims that it is the only macro product that can wait for a page to finish loading! That’s a pretty bold statement to make, and quite clearly untrue. I’m not even sure if that’s legal. If nothing else it is misleading and unhelpful.

I’ve always done my very best to make sure we can back up any of our marketing material. I do not believe in making claims that can’t be supported. At MJT we try our best to respond to queries as honestly and helpfully as possible and have been known to suggest an alternative product if we think ours isn’t suited to the customer’s needs exactly. So I was quite surprised to see a competitor making such blatently false statements. But I don’t see it doing them any favours. Software buyers are pretty savvy people these days and will see through hype like that. I hope.

December 29, 2005

Automated Software Testing

Filed under: Automation, Testing — Tags: — Marcus Tettmar @ 4:36 pm

People have been using Macro Scheduler for Automated Software Testing and Load Testing for years. I’ve often been asked the best way to do this, and I’ve finally gotten around to putting some articles together on how best to use Macro Scheduler for automated testing. You’ll find them here:
http://www.mjtnet.com/automated_testing.htm

Automated Software Testing:
http://www.mjtnet.com/AutomatedTesting.pdf

Automated Load Testing:
http://www.mjtnet.com/loadtesting.pdf