QA Wizard Pro scripts can be run unattended by saving them as batch script files and using the Windows Task Scheduler to launch them at a scheduled time. The Scheduled Task Wizard gives you the option of running the script once at a specified time, or on a daily, weekly or monthly basis. But what do you do if that doesn’t fit your schedule? Perhaps you would like to monitor a web site and ensure it is up and running by logging in once every hour. To set this up for a twenty-four hour period, you would need to schedule 24 separate tasks to run at a specified time – a time-consuming task in itself. If the launch time changes, you would need to go back and modify each of those tasks individually. A better idea is to create another QA Wizard Pro script that allows you to launch the batch script file at a time interval you choose, as well as capture additional information such as total number of times the batch script was run or the number of times the login test failed.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
A QA Wizard Pro batch script (.qawbatch) allows you to extend your testing time since you can schedule the script to run overnight when you are out of the office. If you use TestTrack TCM, you can also attach the batch script to a test case to create a unique copy of the script for each generated test run. You can then launch the batch script from TestTrack TCM directly or via the TestTrack TCM scheduler. The QA Wizard Pro Report that is generated is automatically attached to the test run. You can make this process even more flexible and powerful when you take advantage of the parameters that can be included with the batch script.
Continue reading…
The quickest and easiest way to pass a variable value between scripts is to create a repository variable. A repository variable is a sort of “global variable”, accessible by all scripts that interact with an application. Repository variables are by default defined as text values, but can be converted to any type needed using the appropriate function or simply assigned a non-text value.
Continue reading…
You can use the RunCommand statement in a QA Wizard Pro script to launch a DOS command from the Windows command line. The information required for a RunCommand statement includes:
- Executable path
- Working directory
- Command line arguments
A good test case describes the steps to be taken to perform a particular test. Most of these steps will involve the application under test, but there are also typically some set-up tasks to do prior to running the test, and clean-up tasks once the test is complete. These tasks may include copying over a fresh set of test data, clearing the browser cache, or killing off any hanging application processes. When you automate a test case you are focused on capturing your interactions with the application and verifying the application’s response, so the set-up and clean-up tasks usually get done manually. By thinking outside of the (application) window you can easily add many of these tasks to a script, saving you even more time.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponThe quality of a product relies heavily on the quality of its ingredients. Ignoring one particular ingredient when creating automated test scripts can leave you with a set of “half-baked” scripts that require constant maintenance – some scripts run once successfully but fail after that, while others may contain the same sequence of steps that all need to be modified if a change needs to be made. A little RUMM at the start of the script development process will save you a lot of time and frustration in the future.
Continue reading…
You’ve probably seen and used regular expressions before, even if you’re not aware of it. When you search for all your digital photos (*.jpg) or list all files starting with the letter “a” (a.*) you are using a pattern language known as regular expressions, or regex. You may also not be aware that you can also use regexes in your QA Wizard Pro scripts to perform tasks, such as validating field data or verifying results, and also to ignore dynamic data in properties used as search criteria.
Continue reading…
Reducing lag time between testing and resolving problems is critical. Email notification of test results gets the necessary information to the appropriate person in a fast, direct manner. Here are two ways to email tests results in a QA Wizard Pro script:
Continue reading…
Creating external datasheets allows QA Wizard Pro to use outside data to drive a script. The tester specifies the table or query to populate the datasheet, and must manually modify the properties to select a different set of data. It is possible locate a particular record using a database checkpoint to match a particular value (Creating Database Checkpoints in QA Wizard Pro), but some testers may want to modify existing queries automatically from the script itself.
Continue reading…
Creating QA Wizard Pro batch script files is an ideal way to run scripts unattended. However, it is possible for a script in a batch file to fail and prevent subsequent scripts from running. The failed script may leave multiple instances of the application open, or an unexpected popup window may grab focus and prevent the application from shutting down gracefully.
Continue reading…
