The Seapine View

QA Wizard Pro 2012 includes stress testing, which allows you to disable your network adapter or even limit the available memory while you are running your automated scripts. You’ll now be able to see how your application will respond when the host operating system runs out of disk space or loses network connectivity. You can also limit the amount of available memory.

Watch the following video to learn how to use stress testing and see an example of how an application’s behavior changes when certain stress features are enabled.

Running scripts in a clean environment is critical to ensuring that you’re able to gather the best and most precise results possible. For instance,  let’s say you’re running a series of twenty-five scripts but the first one fails, leaving a browser window open and the user logged in. This can cause successive scripts to fail because they can not log in to the application.

To make sure your scripts run without interference from applications or browser windows that are left open by other scripts, you can add a Windows taskkill command to the beginning of each script. This one line of code ensures that any running application processes are killed.

Continue reading…

While a QA Wizard Pro load test is running, a great deal of activity is occurring on your web server. You can use built-in performance tools on the web server to better pinpoint the type of stress that load testing is causing your server. This information allows you to better identify which pieces of your web application may be causing your server the most pain.

Watch the following video to see how to create and correlate this data.

When load testing against a web application, you may want to create a set of scripts that simulates what activities most users perform. After using your web metrics to determine where users spend their time, you can create a script for each common user action. Using the QA Wizard Pro Load Testing options, you can then match up how often your scripts are run as compared to how many users actually perform those actions.

Watch the following video to see details on how to set this up.

Standardizing your test case layout and wording has always been hard to achieve. Starting with the 2012 release, if you use TestTrack TCM and QA Wizard Pro, you can now  record test case steps as you interact with an application in QA Wizard Pro. Recording steps saves time when you need to document longer tests and reduces the possibility of incorrect or incomplete test cases. It also means that steps, like clicking on a button or typing text in a text box, will always use the same wording in your test cases.

Watch the following video to see this new feature in action.

Beginning with the release of Seapine ALM 2012, if you use both TestTrack TCM and QA Wizard Pro, you can now create automated scripts from test cases. This helps save time when creating scripts because you don’t need to swtich between applications. It also automatically links test cases and scripts.

Continue reading…

We’re very excited to release beta versions of our Seapine ALM suite of products, including TestTrack Pro, TestTrack RM, TestTrack TCM, Surround SCM and QA Wizard Pro! The betas are open to anyone, so feel free to click through and try them out. If you do try them out, please leave feedback so that we can continue to improve our product offerings.
Continue reading…

QA Wizard Pro reports always contain a starting and ending time, which is useful for understanding how long the script took to run. However, if you want to time specific sections in a script you can use the Stopwatch functions to return time in milliseconds or in HH:MM:SS format.

Continue reading…

During testing, many applications create data, such as order numbers and totals, that may be needed later. Instead of only printing the data or verifying the format is correct, you can write the data to a CSV file so you’ll be able to access it again. In this example, we’ll use the “Web 02 Call” script in the QA Wizard Pro Sample Workspace to  call the “xx Print Ticket Number” script (see Figure 1). The “xx Print Ticket Number” script prints the generated ticket number to the output window. In addition to printing the ticket number, we’ll also use the AppendToFile statement to save it to a file so the data can be used by another script.

Continue reading…

Although QA Wizard Pro supports a large number of third-party controls and technologies, there are always ones that our customers are working with that we haven’t quite gotten to. This is where our .Net invocation technology can really come in handy.

QA Wizard Pro’s .Net invocation allows you to call methods and access properties on .Net objects. This not only allows you to get at information that isn’t readily available to the user interface, but also to interact with controls that QA Wizard Pro doesn’t know about.

Continue reading…