To design web pages and web applications, you use a scripting language. Script code adds interactivity to your pages and can respond to events, call methods and change run-time properties. Code written in a scripting language is similar to code written in a traditional programming language. The difference is that script code is executed by a host application.

You can use AQtime Pro to profile scripts executed by the Microsoft Scripting Engine. The engine supports the VBScript and JScript languages and is used by applications like Internet Explorer, Windows Script Host or TestComplete. Thus, you can use AQtime Pro to profile VBScript and JScript routines that are executed in these applications. For instance, you can profile scripts that reside on your web pages or you can profile scripts of your TestComplete project.

Scripts can often be ineffective, which affects the routine’s performance:

• A bad code structure. For example, script code may call a function or execute some statements that can be called or executed out of the loop.
• The eval function is a potential error source during dynamic code generation, since the JScript engine may raise exceptions.
• Useless string concatenations may slow down the script execution.

With AQtime Pro you can detect these problems, optimize your scripts and make them run faster.

To profile a script, you should launch the host application under AQtime Pro and then execute the script in that application. To analyze scripts, you can use the Performance, Coverage, Light Coverage and Function Trace profilers to help you —

• Determine how many times a routine or line was called.
• Find the time spent executing your script code, routines and individual lines.
• Determine what function was called by a routine and what functions it called.
• Find the cause of exceptions that occurred in your code.
• Find and explore the call routes for a routine.
• And much more.