BlazeMeter 3.4 adds step-level labels from Playwright test.step() definitions, giving release owners actionable timing and pass/fail evidence for individual user actions rather than one result for an entire flow.
More diagnostic Playwright performance results
Performance reports now generate labels from logical Playwright steps. A checkout flow, for example, can expose separate results for authentication, product search, cart updates, and payment instead of aggregating every action under one test-level label.
This matters at release gates because teams can isolate the action that drove a latency increase or failure rate. It also improves communication between QA, engineering, and application owners: the report identifies the affected transaction step, not just the broad test scenario.
The label behavior is configurable in YAML. Teams can choose the new per-step labels or retain whole-test labels where existing dashboards, baselines, or service-level reporting depend on the prior format.
Governance considerations include:
- Define consistent
test.step()naming conventions for reporting and audit review. - Set baseline ownership before changing label granularity in trend dashboards.
- Update release criteria where step-level thresholds are more meaningful than test-level averages.
- Preserve YAML configuration in source control with the performance test assets.
API Monitoring workflows with less manual rework
API Monitoring can now import a simple ZIP file containing one or more Postman collection JSON files at the top level. Previously, teams often needed Postman-native ZIP exports; the added option makes it easier to onboard collections supplied by development teams, third parties, or internal API owners.
