AQtime - Setup and Test Management Interfaces (or, Control What to Profile and When)
With AQtime, you are able to target and profile your whole application,
or just specific regions (called areas). You can also use
triggers and actions to specify application execution
points which turn profiling on or off. Unlike triggers, actions
turn on or off the profiling of all threads, rather than only the
current thread. In addition, actions can be used to get profiling
results at the desired application execution points. AQtime’s areas,
triggers and actions give you the flexibility to profile
an exact part of your application when you need
to.
To help you in setting up a profiling session, AQtime provides
a detailed hierarchical list of all elements which are part of your
project: assemblies, modules, namespaces, classes, routines and
individual source files, all categorized for quick and easy retrieval.
AQtime includes three predefined areas: Full Check, Profile Entire Script Code and Profile Entire .NET Code.
If you select Full Check, AQtime will profile all of the routines in all
modules that are added to the Setup panel.
Profile Entire Script Code enables profiling of all routines executed by
the Microsoft Script Engine. That is, you can profile scripts launched by TestComplete, web browser
or any other application that uses this engine.
Profile Entire .NET Code enables profiling of all .NET
modules and assemblies even if they are not included in any
profiling area.
Any of these areas lets
you select one of the following profiling levels: routine, line or class.