Going Beyond Macros…kind of
As the QA guy I'm always looking for tools to automate my testing to make things easier and quicker (not too mention easier to spot problems). My first macro tool was iMAcros for firefox which has to be the coolest thing since sliced bread. Then Drew found Xenu which was like another heaven sent goodie for finding errors and stuff. And of course we have always been using a web checking service to monitor for downtime and the like.
Well, last month I found a pretty powerful tool in order to do all that stuff. I just needed to build it. The tool is called Autoit v3. To quote from their website:
AutoIt v3 is a freeware BASIC-like scripting language designed for automating the Windows GUI and general scripting. It uses a combination of simulated keystrokes, mouse movement and window/control manipulation in order to automate tasks in a way not possible or reliable with other languages (e.g. VBScript and SendKeys). AutoIt is also very small, self-contained and will run on all versions of Windows out-of-the-box with no annoying "runtimes" required!
After learning how to manipulate windows and create a few COM objects I've come up with a tool that I've already used to check the links and search for errors on the sites. So here it is for beta testing and criticism, the Link-O Matic website checker.
it's configurable, supports a proxy, searches for a string on a site's page, has customizable error reporting, and even email alerts. And it even plays the tada wav upon completion.
Missing is documentation so if you have questions you'll have to ask and I have yet to create a GUI so the only feedback it gives is a tray popup box which can be kind of annoying.
Print This Post
November 24th, 2008 - 16:48
Well, I found my first bug. You need to create a folder called ‘logs’ in the same directory as the program if you want a report.