AutomatedQA products serve the entire software project lifecycle:

By using some or all of these tools together you can go beyond simple "testing", "profiling" or "issue-tracking". For instance, when you integrate AQtime with TestComplete, you can debug and tune your applications using test automation, thereby reducing the amount of time spent on manual testing and data analysis.

By using AQtime, TestComplete, Automated Build Studio and AQdevTeam together, you are well on your way to eliminating the most tedious aspects of the development and delivery processes - from automating your software builds, to running your regression test batteries, reporting bugs and tuning the application for optimum efficiency and speed.

Integrating AQtime and TestComplete

Both AQtime and TestComplete are intended to help you improve your application's quality. However, they do this in different ways:

Since TestComplete can record and then simulate user actions in the application under test, you can use TestComplete scripts to simulate user actions over the application that is being profiled by AQtime. Use of TestComplete frees you from performing the test actions (mouse clicks, key presses, and much more) manually.

You can start an AQtime profiler over the application under test directly from TestComplete's script or user interface, and thus use profiling as part of the testing process. At the end of the test run, you get two test logs: the profiling results in AQtime and the script results in TestComplete.

TestComplete contains special programming objects that let you start AQtime profilers, control the profiling run and generate the results. Using these objects you can automate AQtime ver. 2 - 5 (including AQtime .NET Edition 1.2x). The only requirement is that the corresponding AQtime version has to be installed on your TestComplete computer. For instance, you can use the Coverage profiler to determine which part of your source code was tested by your script; the Allocation and Resource profilers let you ensure that your application releases all allocated objects and memory blocks after it is terminated.

After the test run is over, you will have two result sets: one in TestComplete and another one in AQtime. The profiler also posts a link to a file with brief profiling results to the TestComplete log:

Integration of AQtime and TestComplete with AQdevTeam and Automated Build Studio

Though integration of profiling and testing lets you save time and often energy, these are not the only benefits of using AutomatedQA products. Both AQtime and TestComplete are integrated with AQdevTeam, AutomatedQA's project management and issue tracking software.

If test results in TestComplete indicate a bug or an issue in the application under test, you can manually post these results to AQdevTeam directly from TestComplete so that developers will be able to examine the problem carefully and fix it.

To post a bug report to AQdevTeam, you set up properties for a CreateWorkItem template in TestComplete and then simply select the Create Issue item from the context menu of TestComplete's test log.

The template properties define the project, to which the bug report will be posted, the type of the report, subjects and other fields. TestComplete attaches the file with test results to create a bug report.

An advanced way to integrate AQdevTeam with AQtime and TestComplete is to use macros. Via AQdevTeam's Visual Macro Builder, you can quickly profile your application with AQtime and test it with TestComplete or TestExecute at desired intervals as well as at arbitrary moments.

For instance, you can start profiling your application in AQtime and then, instead of reproducing the required user actions manually, have TestComplete simulate these actions. A more sophisticated example: at the end of a workday, AQdevTeam can automatically build your project, run it through AQtime's profilers then execute your test batteries via TestComplete and log all results directly within the AQdevTeam database. This can all be done without writing a single line of code! All of the information needed to profile or test your project – project name, profiler name, name of the file to save results to, etc. – are specified using our advanced Operation Properties dialog:

AQdevTeam is all about optimizing workflows and processes. By automating routine and tedious tasks such as nightly builds, regression test batteries, and performance profiling, it allows you to focus on more important issues.

A similar approach of integrating TestComplete, AQtime and AQdevTeam together is used in Automated Build Studio. Like in Visual Macro Builder macros, macros in Build Studio can include operations that work with the corresponding tool by AutomatedQA Corp. These operations profile your applications with AQtime or AQtime .NET Edition, test them with TestComplete or TestExecute or post new items (bug reports, suggestions, tasks, etc.) to an AQdevTeam database.

The integration of AutomatedQA's tools has been engineered to give you a cohesive way to test your applications from inception to delivery. Use them together with AQdevTeam or Automated Build Studio, and you'll be able to fully automate your organization's build/profile/test/deploy processes.