Traffic Recorded
Note: The legacy Traffic workflow has been replaced by Instant Replay. The articles in this section document the original Traffic workflow for reference and legacy environments. For the current network traffic capture and replay capabilities, see Traffic - Instant Replay.
Legacy Traffic Workflow
What was Traffic?
Traffic was Appvance IQ's HTTP traffic recorder. It provided an alternative to Appium-based testing for load and performance testing of mobile applications by capturing and replaying application network traffic rather than interacting with the application UI.
AIQ used an HTTP proxy to capture traffic from a browser or mobile device and convert the captured requests and responses into a HAR script. The resulting HAR script could then be replayed as part of a performance or load test without requiring the test flow to be implemented manually.
How did it work?
The legacy Traffic workflow consisted of three main steps:
- Connect - configure a browser or mobile device to use the AIQ HTTP proxy.
- Record - perform the actions to be tested while the proxy captured the network traffic and mark meaningful steps, such as "Login" or "Purchase."
- Analyze - save the captured traffic as a HAR script and generate reports for analysis.
The resulting HAR script could then be used in a scenario for performance or load testing.
Example
For example, a team could load-test the login flow of a mobile banking application by connecting a mobile device to the AIQ proxy and recording the login process. AIQ would capture the HTTP requests generated by the application and produce a HAR script that could subsequently be replayed with multiple virtual users to evaluate server behavior under load.
Current Workflow
For new implementations, use Traffic - Instant Replay instead of the legacy Traffic workflow.
Instant Replay captures network activity while recording UX tests in Test Designer, providing the current approach for combining UI test recording with network traffic capture and replay.
Legacy Prerequisites
The following prerequisites applied to the original Traffic workflow:
- An AIQ instance with the legacy Traffic feature enabled.
- A browser or mobile device that could be configured to use the AIQ HTTP proxy.
- The proxy port reachable from the browser or device.
- An SSL certificate installed on the device when HTTPS traffic needed to be captured.
Sections in this book
Current workflow
- Traffic - Instant Replay - captures network activity while recording UX tests in Test Designer and replaces the legacy Traffic workflow.
Legacy workflow
- Traffic - Connect - configure the proxy and connect a browser or device.
- Traffic - Record - capture HTTP traffic and mark steps.
- Traffic - Analyze - generate reports from captured traffic.
- Traffic - Running a Complete Scenario - end-to-end example using the legacy Traffic workflow.
Device setup
- Android - Proxy Settings
- Android - Installing Certificates
- Android - Bypass Proxy Exceptions
- iOS - Proxy Settings
- iOS - Proxy Settings and PAC Files
- iOS - Generating Certificates
Security and troubleshooting
- Traffic - Managing SSL Certificates
- Browsers - Bypassing HSTS Warnings
Last reviewed: August 2026
This documentation describes the legacy Traffic workflow. For the current implementation, refer to Traffic - Instant Replay.