|
|
Integrating TestTrack TCM with Automated Testing and Scripting Tools
By Mark Diesburg, Development Manager
Seapine Software
TestTrack TCM integrates seamlessly with QA Wizard to support automated testing. If you use another automated testing or scripting tool, you can also schedule and run automated script files through the use of a separate executable, known as a script agent, and a text file for communication between the script agent and TestTrack TCM.
About the script agent
Automated script files are run by other applications called script agents. The QA Wizard script agent, QAWAppAgent.exe, is used to run QA Wizard batch files (.qawbat). When you install TestTrack TCM, QAWAppAgent.exe is installed in the ScriptAgents folder in the client applications directory. For example, in Windows the default directory is
C:\Program Files\Seapine\TestTrack\ScriptAgents.
A local setting is automatically added to TestTrack TCM to set the QAWAppAgent.exe as the default application for *.qawbat files. An entry for *.xml files to use the <Associated application> is also automatically created so that QA Wizard report files are automatically opened in Internet Explorer.
To use TestTrack TCM with another scripting or automated testing tool, a new script agent needs to be written to run scripts for that testing tool. The script agent also needs to be added to the ScriptAgents folder and the local TestTrack TCM options.
About the text file
A text file, named .trjob, is used as the communication mechanism between the script agent and TestTrack TCM. When you run or schedule a script file, a sub-folder is created in the ScheduledScripts folder for the running of that script file. By default, the ScheduledScripts folder is created in the TestTrack TCM client directory in Windows and Seapine home directory in UNIX. This location can be changed by adding a ScheduledScriptPath key with the new path to the TestTrack client registry or .conf file.
When a script file runs, it is extracted to the sub-folder and a .trjob file is created for the script file. The result files are also added to the sub-folder. When you attach result files from a script file to a test run in TestTrack TCM, the corresponding sub-folder is also zipped and attached to the test run.
The .trjob file is used by the script agent to communicate back to TCM what the status of the script execution is. The format of the .trjob file is as follows:
The following name value pairs are used to associate the script file back with the test run to attach results. These values should NOT be changed by the script agent:
- ProjectName - contains the name of the project that the script file came from
- ProjectID - contains the record ID for the project
- TestRunName - contains the summary for the test run that the script file came from
- TestRunID - contains the record ID for the test run that the script file came from
- ScriptName - contains the name of the script file
- ScriptType - identifies whether the script file was a file attachment or source code file
The following name value pairs should be updated by the script agent:
- Status - indicates script status. Defaults to 'Waiting' when the .trjob file is created. The script agent should change this to 'Started' after it has started running the script file. The script agent should then change this to 'Passed', 'Failed', or 'Indeterminate' after the script has finished running. 'Indeterminate' means that the script file was not successfully completed.
- StartedOn - contains the script start date and time
- CompletedOn - contains the script finish date and time in
- MainResultFile - contains the relative location of the main report file for the script results
QAWAppAgent.exe source code
The QAWAppAgent.exe is a standard Win32 application that performs the actions for running a .qawbat file. The source for this application can be downloaded here. The ScriptAgents folder also contains a QAWBatAgent.bat and QAWBatAgent.vbs file that can be used as an example.
Surround SCM 5: Getting you Home on Time
By Sarah Wigser, Technical Publications Manager
Seapine Software
The releases of Surround SCM 5 and TestTrack 7.6 have been scheduled for months. The development, QA, and technical writing teams have finished their work. Seapine's support and sales teams are eager to help customers.
It's 8:00 p.m., hours before the releases, and Seapine's Web development team has worked hard hustling to make, review, and test changes. Yet, they are confident that the Web site is ready to go because the team utilized Surround SCM 5's new configurable workflow.
Every time Seapine releases a new product or upgrades an existing product, there are countless Web site changes that occur. Existing copy is updated, new copy is written, feature screenshots and product tours change, evaluation forms and automated emails are updated, new pages are created and old pages are removed, and links change. In addition, all these changes must be reviewed and tested before any files are published.
Read the full article
Best Practices: Building a Test-Driven Development Team
by Stephen Swoyer, Technical Publications Manager
Application Development Trends
It's no secret that many programmers disdain software quality assurance (QA) testing. From feeling it's beneath them to resenting the overall tedium and onerous nature of testing—let alone the time it takes and delays it can add to application delivery—for a lot of code jockeys, software QA testing is just plain anathema.
Not all programmers feel this way, of course. Thanks to the rise of test-driven development (TDD) and other agile approaches to software development, more and more IT pros have come to embrace testing as a way to accelerate development and improve overall quality levels. Now that development tools vendors have started to deliver testing-friendly toolsets—complete with canned support for unit and functional testing during the application development process—it might be just a matter of time before QA testing comes down from its pointy-headed peak and back home to the programming pit.
Read the full article
Seapine News
- The development tools you've read about in this issue of ALM Insider are now available, including TestTrack TCM, Surround SCM 5, and TestTrack Pro 7.6. To learn more, download an evaluation copy, or sign up for a demonstration, visit www.seapine.com/products.
- If you use the TestTrack SDK, make sure you check out the new Lab. It includes set up, reference, and troubleshooting information. You can also contribute examples and other information to the SDK Wiki.
- Earlier this month the Cincinnati Enquirer recognized Seapine as one of the Rising Stars in the Deloitte Cincinnati USA 100, which is the newspaper's annual recognition of the top privately held regional companies. Read the full article.
New Knowledgebase Articles
Seapine's knowledgebase is a great place to find answers to technical questions and learn more about using our products.
Seapine Blogs
Be sure to check out the Seapine employee blogs for alternative observations and varied viewpoints on a myriad of topics.
|
