When to Use Verification Checks

Application errors often do not result in erroneous HTTP responses. More commonly, applications respond with incorrect data values or error messages that are incorporated into HTML content, such as Servlet Exception Occurred or Server Too Busy error messages. Because checks of HTTP status code do not uncover this class of error, application errors are often overlooked unless verification functions that check for non-standard HTTP errors are built into test scripts.

When verifications are built into test scripts, tests go from being simple load tests to hybrid load/functionality tests. Such scripts can be utilized without incurring significant performance loss, even in large load test scenarios. This functionality allows you to detect a class of error that other load tools are unable to detect because errors that occur only under load are undetected with standard load test scripts.

TrueLog Explorer offers the following means of enhancing test scripts with verification functionality:
  • Enabling the Silk Performer Recorder to automatically generate verification checks during recording.
  • Allowing users to apply verification checks visually in Rendered view via a point-and-click interface. No editing of BDL code is required. TrueLog Explorer automatically adds verification functions to scripts.
  • Directly enhancing scripts by manually inserting coded verification functions.
Parent topic: Verification Checks