Skip to main content

What is A/B Testing?

A/B testing lets you route a percentage of live traffic to a test version while the rest continues to the current live version. Both versions produce execution logs, so you can compare their performance with real data before fully switching.

Prerequisites

Before starting an A/B test, you need:
  • A policy group with a currently deployed (live) version
  • A test version that has been published (ACTIVE status)
  • Both versions must belong to the same policy group

Starting an A/B Test

Console

Navigate to the policy group → click Start A/B Test → select the test version → set the traffic percentage.

CLI

The --traffic-rate is the percentage (1–99) of traffic routed to the test version. The remaining traffic stays on the live version.

Monitoring Results

While the A/B test is running, both versions generate execution logs. Compare them using:
Check success rates, match rates, latency, and output variable distributions across both versions.

Adjusting Traffic

Gradually increase the test version’s traffic as you gain confidence:

Stopping an A/B Test

Stopping reverts all traffic to the live version. The test version remains ACTIVE but no longer receives traffic.

Typical Workflow

A/B tests affect production traffic. Start with a low traffic percentage (5–10%) and monitor closely before scaling up.

Next Steps

Impact Simulation

Test against historical data before running an A/B test.

Deployments

Deploy the winning version to production.