[Collapse]AQtime FAQ/viewarticle/63965/
 [Expand]Supported Applications, Tools and Technologies/viewarticle/63964/
 [Collapse]Scripts/viewarticle/63963/
   Why do I get empty results when I profile script code?/viewarticle/8747/
   Can AQtime profile script code?/viewarticle/8748/
 [Expand]Results/viewarticle/63962/
 [Expand]AQtime Trial Version Questions/viewarticle/63961/
 [Expand]Licensing Questions/viewarticle/18515/
 [Expand]Profiling/viewarticle/63959/
 [Expand]Conflicts with Other Software/viewarticle/63958/
 [Expand]AQtime General/viewarticle/63957/
Updated: 7/16/2015 Applies To: AQtime Rating: No votes Click to rate: PoorNot badAverageGoodExcellent
Q.: AQtime does not generate any results when I profile script code. Why?

A.: This may happen by different reasons:

  • First, check the profiler you use. Script profiling is supported by the Performance, Coverage, Light Coverage and Function Trace profilers only.

  • Check whether the tested application uses Microsoft Scripting Engine, since AQtime can only profile those scripts that are executed by this engine.

  • If you profile with the “Attach-to-Process” feature, change the approach and try launching the host application from AQtime (you can specify the host application for your script units in the Run | Run Parameters dialog).

  • Make certain that Microsoft Script Debugger is installed on your computer. Note that there are several versions of the debugger and AQtime may fail supporting some of them. For instance, there is a known problem with script debugger installed by Microsoft Visual Studio 2008. Currently, AQtime cannot use for script profiling Visual Studio’ installation program replaces some debugger modules and after this AQtime stops working with the debugger properly. To avoid the problem, re-install Microsoft Script Debugger after installing Visual Studio 2008.

    To be sure you have the correct version of the debugger, follow these steps:



© 2019 SmartBear Software. All rights reserved.
Email Send feedback on this document