blazemeter-test-data

BlazeMeter Test Data Management

Comprehensive guide for creating, managing, and using test data in BlazeMeter tests.

Overview

Test Data Management in BlazeMeter enables data-driven testing with CSV files, Data Entities, synthetic data generation, and orchestration. This skill covers all aspects of test data from basic concepts to advanced management operations.

Quick Start

1. Core Concepts: Understand Data Entities and Data Parameters
2. Generation: Create synthetic test data with seed lists and functions
3. Management: Manage entities, spreadsheets, and parameters
4. Orchestration: Prepare test environments with Test Data Orchestration
5. Pro: Use Test Data Pro for AI-driven data generation

MCP Tools Integration

Test Data entities are managed through the BlazeMeter UI, but you can use MCP tools to manage tests that use test data:

Available MCP Tools

• Test Management:

  • blazemeter_tests with action read - Read test details including test data configuration
  • blazemeter_tests with action list - List all tests in a project
  • Required args: test_id (integer) or project_id (integer)
  • Returns: Test details including test data entity references

• Test Execution:

  • blazemeter_execution with action read - Read execution details for tests using test data
  • blazemeter_execution with action list - List all executions for a test
  • Required args: execution_id (integer) or test_id (integer)
  • Returns: Execution details and results

When to Use MCP Tools

• Test Management: Manage tests that use test data programmatically
• Execution Monitoring: Monitor test executions using test data
• Automation: Integrate test data testing into automation workflows
• Reporting: Generate reports on tests using test data

Example Workflow

Managing Tests with Test Data:

1. Use blazemeter_tests with action list to find tests using test data
2. Use blazemeter_tests with action read to get test details and test data configuration
3. Use blazemeter_execution with action read to monitor test execution
4. Review execution results to verify test data usage