Considerations for Debugging Tests and Function Libraries in QTP

Share This Post -
  • You must have the Microsoft Script Debugger installed to run tests in debug mode. If it is not installed, you can use the QuickTest Additional Installation Requirements Utility to install it. (Select Start > Programs > QuickTest Professional > Tools > Additional Installation Requirements.)
  • While the test and function libraries are running in debug mode, they are read-only. You can modify the content after you stop the debug session (not when you pause it). If needed, you can enable the function library for editing (File > Enable Editing) after you stop the session. For more information, see Editing a Read-Only Function Library. After you implement your changes, you can continue debugging your test and function libraries.
  • If you perform a file operation (for example, you open a different test or create a new test), the debug session stops.

  • If a file is called using an ExecuteFile statement, you cannot debug the file or any of the functions contained in the file. In addition, when debugging a test that contains an ExecuteFile statement, the execution marker may not be displayed correctly.
  • In QuickTest, when you open a test, QuickTest creates a local copy of the external resources that are saved to your Quality Center project. Therefore, any changes you apply to any external resource that is saved in your Quality Center project, such as a function library, will not be recognized in the test until the test is closed and reopened. (An external resource is any resource that can be saved separately from the test, such as a function library, a shared object repository, or a recovery scenario.)
  • In contrast with this, any changes you apply to external resources saved in the file system, such as function libraries, are implemented immediately, as these files are accessed directly and are not saved as local copies when you open your test.