AQtime Changelog

What's new in AQtime 6.0

Oct 29, 2008
  • Profiling scripts. Now you can use AQtime to profile scripts executed by the Microsoft Scripting Engine. These, for example, include VBScript and JScript routines located on web pages as well as TestComplete scripts. To profile a script, you should launch the host application under AQtime and then execute the script in that application. AQtime recognizes the script’s activity and reports its results along with the application results. Currently, scripts can be profiled with the Performance, Coverage and Function Trace profilers. For more information about this, see Profiling Scripts.
  • Optimization of function parameters retrieval. The Function Trace profiler has been optimized to increase its performance when gathering the values of function call parameters. In previous versions, these values were collected from the entire application if the Get parameter info profiler option was enabled. As a result, a lot of memory was required to collect the results, which slowed down the profiling process significantly.
  • In AQtime ver. 6, this feature is in the profiling area settings. Now including areas have the Retrieve parameter values property. If the property is enabled, the Function Trace profiler only logs the actual parameter values for the functions that belong to the area. Thus, the profiler only inspects the routines you are interested in.
  • Filtering out standard units. Most development environments include their standard libraries in applications. The library routines perform a lot of auxiliary tasks, interact with classes and controls, draw forms, and so on. However, generally, profiling of standard units does not make a lot of sense, since their code cannot be modified. To only focus on your code, you can exclude standard libraries from profiling. This functionality can be enabled via the Exclude standard source files option, or via the Exclude Standard Source Files button of the Setup panel.
  • Extended .NET code debugger. AQtime can now obtain a call stack for .NET routines, trace specific .NET events and display this information in the Event View panel. This functionality is available if the Use extended debugger for managed code option is enabled.