Skip to main content

Traffic Recorded

Note: The legacy Traffic featureworkflow has been replaced by Instant Replay. The articles belowin this section document the original Traffic workflow;workflow for reference and legacy environments. For the current capability,network traffic capture and replay capabilities, see Traffic - Instant Replay.

Legacy Traffic Workflow

What iswas Traffic?

Traffic iswas Appvance IQ's HTTP traffic recorder. ForIt provided an alternative to Appium-based testing for load orand performance testing of a mobile application,applications anby Appium-basedcapturing approachand is far too resource-consuming. A better solution is to simulatereplaying application network traffic byrather sendingthan interacting with the requestsapplication and verifying the responses.UI.

To capture those requests, AIQ usesused an HTTP proxy thatto records thecapture traffic from a browser or mobile device and transformsconvert itthe captured requests and responses into a HAR script. containingThe the requests and responses. This staticresulting HAR script cancould then be replayed toas runpart of a performance/performance or load test,test without writingrequiring a single line ofthe test code.flow to be implemented manually.

How doesdid it work?

The legacy Traffic workflow hasconsisted of three main steps:

  1. Connect - configure a browser or mobile device to use the AIQ HTTP proxy (port 9095 by default).proxy.
  2. Record - perform the actions you want to testbe tested while the proxy capturescaptured the traffic,network traffic and mark meaningful stepssteps, (forsuch example,as "Login" or "Purchase").Purchase."
  3. Analyze - save the captured traffic as a HAR script and generate reports tofor review it.analysis.

The savedresulting HAR script iscould then be used in a scenario as afor performance or load test.testing.

Example

SupposeFor youexample, wanta toteam could load-test the login flow of youra mobile banking app.application Youby connectconnecting youra phonemobile device to the proxy,AIQ record yourself logging in,proxy and recording the login process. AIQ captureswould allcapture the HTTP requests.requests Thegenerated capturedby trafficthe becomesapplication and produce a HAR script that youcould cansubsequently replaybe replayed with manymultiple virtual users to see how theevaluate server behavesbehavior 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 available under Record > Traffic.enabled.
  • A browser or a mobile device (Android or iOS) that cancould be configured to use the AIQ HTTP proxy.
  • The proxy port (9095 by default) reachable from the browser or device.
  • An SSL certificate installed on the device ifwhen youHTTPS needtraffic needed to recordbe HTTPS traffic.captured.

Sections in this book

Main

Current workflow:

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 withusing Firefoxthe legacy Traffic workflow.

Device setup:

setup

Security and troubleshooting:

troubleshooting

Last updated:reviewed: FebruaryAugust 17, 20232026

IfThis youdocumentation havedescribes anythe feedbacklegacy onTraffic thisworkflow. topic,For pleasethe contactcurrent usimplementation, atrefer documentation@appvance.aito Traffic - Instant Replay.

Back to top