BlazeMeter 3.5 automatically splits CSV test data across browser-test engines, giving release owners unique user datasets without manual file preparation. The change reduces a common source of invalid multi-engine results: repeated test identities, accounts, or transactions assigned to more than one engine.
Unique test data for browser-based testing
Scripted and scriptless browser-based tests can now distribute splittable CSV data automatically across engines. Each engine receives a distinct, non-overlapping subset, matching the established Split CSV behavior for standard performance tests.
For teams operating distributed browser tests, this changes the preparation workflow:
- Remove manual pre-splitting of source CSV files.
- Reduce the risk of concurrent engines using the same credentials or records.
- Preserve per-engine CSV files in engine artifacts for investigation.
- Enable the Split CSV option in the scriptless editor when eligible data is present.
This is particularly relevant where test data represents customer-like records, inventory, payment tokens, or other finite datasets. Unique allocation improves confidence that observed failures reflect application behavior rather than test-data collisions. Artifact retention also gives QA leads a practical audit trail when reviewing a failed run.
Faster API Monitoring for critical services
API Monitoring now offers an Every 30 seconds schedule in a monitor's Daily schedule on eligible paid plans. This is the first supported frequency below one minute; existing schedules from one minute to one day are unchanged.
