Skip to content

UI Views Reference

Load Tester uses an Eclipse-based interface with multiple views (panels) that display different aspects of your test cases, load tests, and results. If you've ever opened the Window menu and wondered what half the views are for, this is your guide.

Each view serves a specific purpose in the load testing workflow. This reference describes what each one shows and when you'll want it open.

Opening Views

To open any view:

  1. Click: Window → Show View
  2. Select the view you want to open

Views can be dragged, docked, stacked as tabs, or left floating. Your layout persists between sessions.

Project & Navigation Views

Purpose: Browse all test cases, datasets, load configurations, and results in your repository.

What it shows: - Repository tree (.wpt file) - Test Cases folder with all test cases - Datasets folder with CSV files - Load Tests folder with load configurations - Results folder with completed load test results

When to use: - Opening test cases for editing - Creating new test cases or datasets - Accessing load test results - Organizing project structure

Related topics: Navigating the UI

Test Case Editing Views

Test Case Editor

Purpose: Edit test case structure, view HTTP transactions, configure correlation and field assignments.

What it shows: - Hierarchical test case structure (web pages → transactions → content) - HTTP requests and responses - Configured extractors, validators, and field modifiers - Think time between pages

Key features: - Drag-and-drop to reorder pages - Right-click for ASM, validation, extractors - Color coding: green (customized), grey (ASM-configured), white (recorded) - Transaction tree with expand/collapse

When to use: - Viewing test case structure after recording - Configuring correlation and fields - Running ASM wizard - Adding/removing transactions

Related topics: Inspecting a Recording, ASM Overview

Headers View

Purpose: View and edit HTTP request/response headers for selected transaction.

What it shows: - Request line (HTTP method, URL, version) - Request headers (User-Agent, Authorization, Content-Type, cookies, etc.) - Response status line (HTTP version, status code, reason phrase) - Response headers (Set-Cookie, Content-Type, Cache-Control, etc.) - Modifier indicators (icons showing fields configured for parameterization)

Key features: - Edit request line and URL parameters - Double-click to edit header values - Configure datasets/extractors on any header - Export request or response for debugging

When to use: - Debugging authentication issues (checking Authorization headers) - Configuring dynamic session tokens (cookies, bearer tokens) - Editing URL query parameters - Verifying HTTP method (GET, POST, PUT, DELETE)

Related topics: OAuth & Bearer Tokens, Advanced Configuration

Content View

Purpose: View and interact with HTTP request/response bodies.

What it shows: - Request content (form data, JSON, XML, file uploads) - Response content (HTML, JSON, XML, images, raw bytes) - Multiple tabs: HTML/XML (rendered), Text (source), Image, Raw (hex dump)

Key features: - Interactive HTML rendering - click form fields to configure them - Automatic content decoding (gzip, deflate, Brotli) - Export content to file (HTML, text, image, raw bytes) - Hex dump mode for binary content - Search within text content

When to use: - Viewing rendered web pages from recording - Configuring form fields (click fields in HTML view) - Examining JSON/XML API responses - Debugging content encoding issues - Exporting content for analysis

Related topics: Inspecting a Recording, Datasets

Fields View

Purpose: View and mass-edit all form fields, URL parameters, and file uploads in test case.

What it shows: - All fields across entire test case (or selected web page/transaction) - Field name, type (query/field/post/part/file), datasource, recorded value - Color coding: white (recorded), green (user-configured), grey (ASM-configured) - Hierarchical or flat view

Key features: - Filter by field name, type, or value - Mass-select and bulk-edit fields - Search with regular expressions - Customizable columns and sorting - "Go to transaction" to find field's location in test case

When to use: - Bulk-editing similar fields (e.g., change all usernames) - Finding all instances of a parameter - Reviewing ASM correlation results - Configuring datasets across multiple fields

Related topics: Datasets, Advanced Field Assignments

Search View

Purpose: Find text, URLs, or header values across entire test case.

What it shows: - Search results with transaction context - Matching text highlighted - Location (URL, header, field name/value, content)

Key features: - Text search with case-sensitivity option - Regular expression support - Filter by location type (URLs, headers, fields, content) - Click result to navigate to transaction

When to use: - Finding session IDs or tokens to correlate - Locating specific error messages - Searching for API endpoints - Finding form field names

Related topics: ASM Overview, Debugging Failed Replays

Dataset & Load Configuration Views

Dataset Editor

Purpose: Create and edit CSV datasets for parameterization.

What it shows: - Spreadsheet view of dataset rows and columns - Column headers (field names) - Data values for each virtual user

Key features: - Add/remove columns - Import from CSV file - Generate data (sequential numbers, random values, UUIDs) - Export to CSV - Validation (check for duplicates, empty cells)

When to use: - Creating user credential datasets - Editing imported CSV data - Generating test data - Verifying dataset completeness

Related topics: Datasets & Data-Driven Testing

Load Test Editor

Purpose: Configure load test settings, user ramps, and duration.

What it shows: - Test cases included in load test - Virtual user count per test case - Ramp schedule (how users are added over time) - Test duration - Think time settings - Advanced options (think time scale, connection pooling)

Key features: - Drag test cases to reorder - Define multi-stage ramps (e.g., 0→50 users in 5 min, hold at 50 for 10 min) - Configure user distribution across test cases - Set global think time multiplier - Enable/disable connection reuse

When to use: - Configuring load profile before test - Adjusting user counts and ramps - Reviewing load test settings - Modifying think time behavior

Related topics: Configuring a Load Test, Load Test Concepts

Results & Analysis Views

Load Test Results View

Purpose: Overview of completed load test with navigation to detailed views.

What it shows: - Test summary (duration, users, total hits, errors) - Quick stats (average response time, hits/sec, bandwidth) - Links to detailed reports and analytics dashboard - Server monitoring data (if configured)

Key features: - Navigate to Statistics View for metrics - Open Analytics Dashboard for interactive analysis - Export metrics to CSV - View legacy HTML reports - Access server monitoring charts

When to use: - First view of test results - Getting high-level test summary - Navigating to detailed analysis - Exporting results

Related topics: Results Overview, Embedded Analytics Dashboard

Statistics View

Purpose: Display metrics charts and tables for load test results.

What it shows: - Response time over time (line chart) - Hits per second over time - Bandwidth over time - Virtual users over time - Error rate over time - Percentile response times (50th, 90th, 95th, 99th) - Metrics by page or transaction - Metrics by user level (concurrent users)

Key features: - Interactive charts with zoom/pan - Switch between metrics (response time, throughput, bandwidth) - Filter by date/time range - Group by page, transaction, or user level - Export chart data to CSV

When to use: - Analyzing response time trends - Identifying performance degradation points - Comparing metrics across user levels - Spotting throughput bottlenecks

Related topics: Understanding Metrics, Performance Analysis Workflow

Replay View

Purpose: View results of single-user test case replay validation.

What it shows: - Replay status (success/failure) - Transaction-by-transaction results - HTTP status codes - Response times - Validation errors - Extraction results

Key features: - Color-coded success/failure indicators - Expand transactions to see details - Click transaction to view in Headers/Content views - Error messages with context

When to use: - Validating test case after ASM configuration - Debugging replay failures - Verifying extractors work correctly - Checking authentication success

Related topics: Running a Replay, Understanding Replay Results, Debugging Failed Replays

Error View

Purpose: Show all errors that occurred during replay or load test.

What it shows: - Error messages - HTTP status codes (401, 403, 404, 500, etc.) - Transaction that failed - Timestamp - Stack traces (for system errors)

Key features: - Filter by error type or message - Sort by frequency or timestamp - Click error to navigate to transaction - Export errors to file

When to use: - Troubleshooting failed replays - Identifying most common load test errors - Debugging authentication failures (401/403) - Finding correlation issues

Related topics: Debugging Failed Replays, Common Error Messages

Monitoring & Status Views

Status View

Purpose: Real-time status during load test execution.

What it shows: - Current virtual user count - Current hits/second - Current error rate - Test elapsed time - Test phase (ramp-up, steady-state, ramp-down)

Key features: - Updates every few seconds - Shows progress bar for test duration - Start/stop/pause controls - Live error count

When to use: - Monitoring test in progress - Verifying test starts successfully - Checking if error rate is acceptable - Confirming user ramp is progressing

Related topics: Running a Load Test, Monitoring During a Load Test

Actors View

Purpose: Monitor individual virtual user status during load test.

What it shows: - Virtual user ID - Current state (idle, executing, waiting) - Current page/transaction being executed - Last action timestamp

Key features: - Real-time status updates - Filter by user state - Click user to see execution details - Shows think time delays

When to use: - Debugging why users aren't executing - Verifying think time behavior - Checking user distribution - Troubleshooting stalled users

Related topics: Running a Load Test, Monitoring During a Load Test

Engines View

Purpose: Monitor cloud load engines during distributed load test.

What it shows: - Engine ID and hostname - Engine state (starting, running, stopping, stopped) - Virtual users assigned to engine - Current hits/second per engine - CPU and memory usage (if available)

Key features: - Real-time engine status - Start/stop individual engines - View engine logs - SSH to engine (for diagnostics)

When to use: - Verifying all cloud engines started successfully - Monitoring engine health during test - Debugging engine connectivity issues - Checking user distribution across engines

Related topics: Cloud Load Testing, Cloud & Engine Issues

Servers View

Purpose: Monitor server performance metrics during load test.

What it shows: - Server name/IP - CPU usage (%) - Memory usage (%) - Disk I/O - Network throughput - Custom performance counters (Windows/Linux)

Key features: - Real-time metric updates - Multiple servers simultaneously - Configure thresholds for alerts - Export metrics to CSV

When to use: - Identifying server resource bottlenecks - Correlating response time with server load - Verifying server capacity limits - Diagnosing performance issues

Related topics: Server Monitoring Introduction, Metrics & Counters

View Layout Tips

For test case configuration: - Test Case Editor (center) - Headers View (bottom) - Fields View (bottom, tabbed with Headers) - Content View (right)

For load test analysis: - Load Test Results View (left) - Statistics View (center) - Error View (bottom)

For live monitoring: - Status View (top) - Statistics View (center) - Actors View (bottom left) - Servers View (bottom right)

Saving Layouts

To save your current layout:

  1. Arrange views as desired
  2. Click: Window → Save Perspective As...
  3. Name your perspective (e.g., "My Configuration Layout")
  4. Click: OK

To switch between saved layouts:

  1. Click: Window → Open Perspective
  2. Select your saved perspective

Quick Reference

Project & Navigation: - Navigator View - browse test cases, datasets, results

Test Case Editing: - Test Case Editor - edit test structure - Headers View - view/edit HTTP headers - Content View - view request/response bodies - Fields View - bulk-edit form fields/parameters - Search View - find text across test case

Configuration: - Dataset Editor - edit CSV datasets - Load Test Editor - configure load profile

Results & Analysis: - Load Test Results View - test summary and navigation - Statistics View - metrics charts and tables - Replay View - single-user replay results - Error View - error messages and stack traces

Monitoring: - Status View - real-time test status - Actors View - virtual user status - Engines View - cloud engine status - Servers View - server performance metrics