New TestTrack features include a new native relational database, custom fields that calculate values, and draft and active custom fields. Surround SCM’s new features include improved offline support, more flexible mainline branches, and additional integrations, while QA Wizard Pro now features stress testing, Google Chrome support, integration enhancements, and more.

In the one-hour webinar, Paula Rome and Grant Lammi, Seapine product managers, will demonstrate the new features in Seapine ALM 2012. When the demonstration is over, you’ll have time to ask questions and learn more.

The webinar is being offered twice to accommodate Europe and North America attendees. The first webinar begins at 2:00 p.m. Western European Time (9:00 a.m. Eastern Standard Time), and the second will follow at 2:00 p.m. Eastern Standard Time (11:00 a.m. Pacific Standard Time).

Join us!

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.

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.

To add the taskkill command, insert a line of code that uses the RunCommand statement to pass the Windows taskkill command to the Command Window at the beginning of the script. The following screenshot includes the code:

A few things to keep in mind:

• The Image Name corresponds to the application process and can be found using the Task Manager.
• Quotes must be placed around the arguments to make sure the command is passed correctly.
• The “/C” option in the argument closes the Command Window when the action is completed.

By adding one line to the script you can guarantee that each execution will run without interference.

For more QA Wizard Pro tips, be sure to check out the QA Wizard Pro Resource Center.

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

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

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

1. In TestTrack TCM, open the test case you would like use for creating your automated script. Click the “Steps” tab and then click the “Create Script” button

TestTrack TCM Create Script

2. QA Wizard Pro starts if it’s not already running. The Create Automated Test Case dialog also opens.

Create Automated Test Case

3. Enter a Script Name, then select a script creation method. For this example, I’m recording a new script with step notes. This option records a script as you perform the displayed test case steps.

4. Next, select the application you want to record the steps against. Then, click “Record” to start recording.

5. The applications starts. The test case steps and expected results are displayed.

6. Perform the steps you want to record.

7. Click “Done” after completing each step to add the actions to the script. If you do not click Done after each step, all the recorded actions are added to the end of the script.

Recording Automated Test Case

8. Click the “Stop” button when you complete all the steps, to finish the recording process.

The script is created. The test case steps, recorded actions, and a hyperlink to the test case are included in the script. Test case steps are added to the script as TestCaseStep statements.

Automated Script in QA Wizard Pro

The new script can now be executed using QA Wizard Pro or even added to a batch file.

What’s New?

Following are some of the highlights of this release. More information is available on the beta site.

• TestTrack now includes support for calculated fields, allowing custom fields to automatically calculate their values based on values in other fields. If you use our native backend database rather than an RDBMS, the format has been changed to SQLite, with a variety of performance enhancements. And, to improve the ability to create test cases, we’ve added QA Wizard Pro enhancements that allow you to automatically record and create your test steps.
• For Surround SCM, we’ve improved our support for offline changes with an enhanced working directory differences dialog and a new sync repository command. Mainline branches can also now have separate configurations from your overall server settings, giving  teams more flexibility. We’ve also added a number of new third-party integrations.
• In QA Wizard Pro, we’ve added support for the Google Chrome browser. A whole new set of testing is also now possible with our new stress testing support, allowing you to test applications in stressed conditions that are difficult to create, such as low disk space and memory, network communication problems, and read-only disk errors.

Register for the Seapine ALM 2012 Betas

In the following example, the startstopwatch and stopstopwatch functions are used to see how long it takes for the BugInfo window to open and be closed.

startstopwatch()
Window("Bug Info").Button("buttonClose").Click()
stopstopwatch()
Window("BugReporter Dialog").Close()

The following steps show how to retrieve the elapsed time and print it to the Output Window.

'Get elapsed time and print to Output Window
X=GetStopwatchElapsedMilliseconds()
Y=GetStopwatchElapsedTime()
println("X = " + X)
println("Y = " + Y)

Following is a sample display of the elapsed starting and ending times for a specific section in a script.

More information about the stopwatch functions is available in the QA Wizard Pro User Guide.

Figure 1: xx Print Ticket Number script

When a ticket number is found, the AppendToFile statement saves it to a text file. In the example in Figure 2, the AppendToFile statement writes the ticket number to a new line in the file. The %SCRIPTS% environment variable in the output file path references the current script directory.

Figure 2: Save the ticket number to a new line

If you want, you can save additional information. In Figure 3, the AppendToFile statement writes the ticket number plus the current date/time, separated by a comma, on a new line.

Figure 3: Save the ticket number plus the current date/time, separated by a comma

After the CSV file is created, it can be accessed as an external datasheet by any other script.

For more QA Wizard Pro tips, be sure to check out the QA Wizard Pro Resource Center.