Traffic Transformation
Transforms adapt recorded traffic for replay: replace credentials, shift dates, or carry a value from one response into a later request. They can also adjust outbound requests and responses used by mocks.
Choose your workflow
| Environment | Saved configuration | Start here |
|---|---|---|
| Speedscale Cloud | Traffic Transform Template | Configure snapshot tuning, then save a reusable template |
| proxymock | Blueprint | Create and Verify Blueprints |
| Local JSON authoring | Bare transform configuration | Test and apply local rules |
These workflows use the same transform engine, extractors, and transforms. A blueprint wraps the transform configuration with local metadata; it is not the same JSON document as a bare Cloud template.
Tune a Cloud snapshot
- Run a small replay against your test application.
- Inspect inbound accuracy failures and outbound mock misses separately. Open the relevant request to understand which value changed.
- Open the snapshot's Tuning tab. Review a recommendation, the transform chains it proposes, and the traffic affected by each chain.
- Apply a targeted change, then replay again to check the result.
Use Traffic to inspect requests and responses, selecting inbound or outbound traffic as needed. A chain that matches no traffic cannot fix the replay. Check its filter and execution side before adding more transforms.
Correctness failures may require an application fix or a new recording. Change transforms only when the difference is an expected consequence of replaying in a different context. For a complete local iteration loop, see Replay Tuning.
Extractors and Transforms
Each chain extracts a value, applies its transforms in order, then writes the result back. See Basic Principles for the execution model and Where to Transform Traffic for generator and responder placement.
Use json_path for JSON, xml_path for XML, and graphql for GraphQL values addressed by semantic path.
Where to Transform Traffic
Generator request chains change what the app receives. Generator response chains can store values returned by the app. Responder request chains affect mock matching; responder response chains affect what the mock returns. The extractor selects the request or response field.
Initialize reusable values with generator or responder variables. Generator variables are scoped to a virtual user. See Variables and Embedded Syntax for storage and runtime references.
Traffic Transform Templates
A Traffic Transform Template saves a Cloud transform configuration for use with later snapshots. Review templates in Traffic Transforms.
How to Use Transform Templates
- Configure transforms for a snapshot and verify them with a replay.
- Save the configuration as a template.
- Select the saved template for another snapshot and review its filters, variables, and credentials before replaying.
The video shows an earlier dashboard layout. Current snapshot tuning is under Tuning, and requests are under Traffic.
For local reuse, save a blueprint. A recording's snapshot ID does not bind a local blueprint; active rules can apply to other recordings in the workspace when their filters match.