BlazeMeter Functional Testing
Comprehensive guide for creating and managing Functional Tests in BlazeMeter.
Overview
Functional Testing in BlazeMeter supports GUI Functional Tests with scriptless creation, YAML upload, and IDE-based development. This skill covers test creation, management, debugging, and browser support.
Quick Start
- GUI Tests: Create tests using scriptless UI, YAML files, or IDEs
- Test Data: Use test data in Functional Tests
- Action Library: Manage shared Objects and Group Actions
- Debugging: Debug tests using best practices
- Browsers: Understand browser support and selection
MCP Tools Integration
Functional Tests are managed through the BlazeMeter UI, but you can use MCP tools to manage tests and executions:
Available MCP Tools
Test Management:
blazemeter_tests with action read - Read test details including functional test 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 functional test configuration
Test Execution:
blazemeter_execution with action read - Read execution details for functional tests
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 functional tests programmatically
- Execution Monitoring: Monitor functional test executions
- Automation: Integrate functional testing into automation workflows
- Reporting: Generate reports on functional test results
Example Workflow
Managing Functional Tests:
- Use
blazemeter_tests with action list to find functional tests
- Use
blazemeter_tests with action read to get test details
- Use
blazemeter_execution with action read to monitor test execution
- Review execution results for functional test outcomes
Reference Files
GUI Tests
- gui-tests.md: Overview, Create YAML File, Create from Java IDE, Create from Python IDE, Report, Duplicate/Delete/Move/Rename Test, Test Data, Parameterize Taurus YAML Scripts, Desired Capabilities Options, Custom JavaScript Actions, Taurus Actions Scriptless
API Tests (Deprecated)
- api-tests.md: Create, Report, Scripting in UI, Create from Existing Script. Note: This feature is deprecated. Use API Monitoring instead.
Action Library
- action-library.md: Test Action Library, Management
Debugging
- debugging.md: Debug Best Practices
Browsers
- browsers.md: Supported Browsers
When to Use Each Reference
- GUI Tests: When creating, managing, or reporting on GUI Functional Tests
- API Tests: When working with deprecated API Functional Tests (use API Monitoring instead)
- Action Library: When managing shared test components
- Debugging: When debugging Functional Tests
- Browsers: When understanding browser support and selection
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: blazemeter-functional-testing3description: Comprehensive guide for BlazeMeter Functional Testing, including GUI Functional Tests, API Tests (deprecated), Action Library, and debugging. Use when working with Functional Testing for (1) Creating GUI Functional Tests (YAML, Java IDE, Python IDE), (2) Managing Functional Tests (duplicate, delete, move, rename), (3) Using test data in Functional Tests, (4) Working with Action Library, (5) Debugging Functional Tests, (6) Understanding browser support, or any other Functional Testing tasks. Note - API Functional Tests are deprecated in favor of API Monitoring. Use when this capability is needed.4---56# BlazeMeter Functional Testing78Comprehensive guide for creating and managing Functional Tests in BlazeMeter.910## Overview1112Functional Testing in BlazeMeter supports GUI Functional Tests with scriptless creation, YAML upload, and IDE-based development. This skill covers test creation, management, debugging, and browser support.1314## Quick Start15161. **GUI Tests**: Create tests using scriptless UI, YAML files, or IDEs172. **Test Data**: Use test data in Functional Tests183. **Action Library**: Manage shared Objects and Group Actions194. **Debugging**: Debug tests using best practices205. **Browsers**: Understand browser support and selection2122## MCP Tools Integration2324Functional Tests are managed through the BlazeMeter UI, but you can use MCP tools to manage tests and executions:2526### Available MCP Tools2728- **Test Management**: 29 - `blazemeter_tests` with action `read` - Read test details including functional test configuration30 - `blazemeter_tests` with action `list` - List all tests in a project31 - Required args: `test_id` (integer) or `project_id` (integer)32 - Returns: Test details including functional test configuration3334- **Test Execution**:35 - `blazemeter_execution` with action `read` - Read execution details for functional tests36 - `blazemeter_execution` with action `list` - List all executions for a test37 - Required args: `execution_id` (integer) or `test_id` (integer)38 - Returns: Execution details and results3940### When to Use MCP Tools4142- **Test Management**: Manage functional tests programmatically43- **Execution Monitoring**: Monitor functional test executions44- **Automation**: Integrate functional testing into automation workflows45- **Reporting**: Generate reports on functional test results4647### Example Workflow4849**Managing Functional Tests**:501. Use `blazemeter_tests` with action `list` to find functional tests512. Use `blazemeter_tests` with action `read` to get test details523. Use `blazemeter_execution` with action `read` to monitor test execution534. Review execution results for functional test outcomes5455## Reference Files5657### GUI Tests58- **[gui-tests.md](skill-blazemeter-functional-testing://references/gui-tests.md)**: Overview, Create YAML File, Create from Java IDE, Create from Python IDE, Report, Duplicate/Delete/Move/Rename Test, Test Data, Parameterize Taurus YAML Scripts, Desired Capabilities Options, Custom JavaScript Actions, Taurus Actions Scriptless5960### API Tests (Deprecated)61- **[api-tests.md](skill-blazemeter-functional-testing://references/api-tests.md)**: Create, Report, Scripting in UI, Create from Existing Script. **Note: This feature is deprecated. Use API Monitoring instead.**6263### Action Library64- **[action-library.md](skill-blazemeter-functional-testing://references/action-library.md)**: Test Action Library, Management6566### Debugging67- **[debugging.md](skill-blazemeter-functional-testing://references/debugging.md)**: Debug Best Practices6869### Browsers70- **[browsers.md](skill-blazemeter-functional-testing://references/browsers.md)**: Supported Browsers7172## When to Use Each Reference7374- **GUI Tests**: When creating, managing, or reporting on GUI Functional Tests75- **API Tests**: When working with deprecated API Functional Tests (use API Monitoring instead)76- **Action Library**: When managing shared test components77- **Debugging**: When debugging Functional Tests78- **Browsers**: When understanding browser support and selection7980---81> Converted and distributed by [TomeVault](https://tomevault.io/claim/blazemeter) — claim your Tome and manage your conversions.82<!-- tomevault:4.0:skill_md:2026-04-11 -->