Home Scripting Verification Points

Verification Points & Checkpoints

Verification Points and Checkpoints ensure that the application is functioning as expected during a load test. Error Handling helps the script to handle expected and unexpected errors gracefully without stopping the test.

Verification Points

Validate that the application response is as expected using checkpoints, content checks, response codes, etc.

Checkpoints

Ensure critical transactions pass. If a checkpoint fails, the virtual user fails and is logged.

Error Handling

Handle expected errors gracefully and continue the test. Capture details for analysis.

Choose Tool

1. Verification Points (How to do & Examples)

LoadRunner (VuGen)

1. Add Verification

In VuGen, go to Add → Verification.

2. Select Type

Choose the verification type: Text / HTML / Image / DB / etc.

3. Configure

Enter the expected value / select options and properties.

4. Place

Place the verification at the appropriate step in the script.

5. Save & Run

Save the script and run. Verify results in Analysis (Replay Status / Log).

Common Verification Types in LoadRunner

Type Use Case Example (What it verifies) Example Value
Text Check Verify text exists in response Welcome user Welcome
HTML Check Verify HTML tag / attribute <title>PerfHub</title> title=PerfHub
Image Check Verify image in response logo.png logo.png
Response Code Check Verify HTTP status code Status code should be 200 200
Database Check Verify data in database Select count(*) from orders where id=123 count > 0
Content Type Check Verify Content-Type header Header Content-Type text/html

LoadRunner – Checkpoints

  1. Add Checkpoint
    Add → Checkpoint
  2. Configure
    Point as checkpoint.
  3. Configure Rule
    Set the rule: Continue / Stop Virtual User on Failure.
  4. See Rule Configure
    Failed checkpoint will mark the iteration as failed.

LoadRunner – Error Handling

1. Add Error Handling

Add → Error Handling.

2. Define Rule

Set conditions (by status code, text, or verification failure).

3. Action

Choose action: Continue / Retry / Skip / Stop Vuser.

4. Log Details

Capture error details using lr_error_message.

5. Analyze

Review in Analysis logs and Error Summary.

Best Practice (LR): Use checkpoints for critical business flows and error handling for expected errors like 404, 500, timeouts, etc., to keep the test stable.

Quick Comparison

Topic LoadRunner (VuGen) Apache JMeter NeoLoad
Verification Points Add → Verification (Text, HTML, Image, DB, etc.) Assertions (Response, JSON, XPath, Duration, Size, etc.) Add Verification (Text, JSON, XML, Status Code, DB, etc.)
Checkpoints Add → Checkpoint (Continue / Stop Vuser on Failure) Assertion failure can stop thread (using options) Add Checkpoint (Stop Vuser / Continue / Mark Failed)
Error Handling Add → Error Handling (Continue, Retry, Skip, Stop) If Controller, JSR223, Try/Catch, Continue on error Error Handling (Continue, Retry, Skip, Stop Vuser, Skip)
Result Analysis Analysis Logs, Replay Status, Checkpoints, Error Summary Listeners (View Results Tree, Summary, Aggregate Report) Reports (Real Time, Detailed Logs, Error Log)

Best Practices

  • Use verification points to validate business critical data.
  • Use checkpoints to stop virtual users on critical failures.
  • Handle expected errors (404, 500, timeouts) using error handling.
  • Log meaningful error messages for easier debugging.
  • Review analysis logs and reports regularly during execution.

Common Errors

  • Not using checkpoints on critical flows.
  • Over-validating (too many verifications) – impacts performance.
  • Ignoring expected errors – leads to false failures.
  • Hard coded values in verifications – use parameterization.
  • Not analyzing error logs during test execution.