April 19, 2010

Rapid Fire Scripting with QA Wizard Pro

Helix ALM
I used to classify drag-and-drop as a "lipstick" feature--one that looked great during product demos but one that nobody actually used. So when I found out we were going to enhance QA Wizard Pro's drag-and-drop capabilities for the 2010.0 release, I was skeptical. Fortunately, I was wrong. On the contrary, I've found that drag-and-drop from QA Wizard Pro's Preview pane makes writing automated test scripts even faster than recording them. Here's how.
  1. Click on a window or control in the application repository. The Preview pane updates with a picture of the window. This picture is interactive.
  2. Click on the control in the Preview pane you want to interact with and drag it into the script. QA Wizard Pro adds an appropriate action to the script.
  3. Repeat Step 2 until your script is done.

QA Wizard Pro Preview Pane Drag-And-Drop

Drag-and-drop "just works" by writing the script you likely intended. It performs a great deal of manual labor for you. For example:
  • The control doesn't have to exist in your application repository. QA Wizard Pro automatically adds the control to the application repository and also automatically selects good search criteria.
  • You don't have to specify an action unless you want to. For example, QA Wizard Pro knows that if you're dragging a button, you probably want to Click on it. If you don't like QA Wizard Pro's guesses, you can drag-and-drop with the right mouse button to be prompted for a specific action.
  • The application you're testing doesn't need to be running. QA Wizard Pro has all of the needed data available offline.  In addition, if you use the Global Repository, this data is available to all users.
Productivity-wise, nothing else compares. In one mouse move you specify a control, an action on the control, and how to search for the control. You're only prompted if you need to provide additional data, such as the text to set in an edit box. When you try it a few times you'll experience this feature's power, both in terms of time spent and ease of use. It's usually more productive than recording scripts--so much so that I now recommend using drag-and-drop from the Preview window for building most automated test scripts.