# A/B testing in Uniform
> Add, change, and remove tests configured on a composition using Uniform Canvas—all without a developer.
Source: https://docs.uniform.app/docs/guides/ab-testing
Optimize your experience with A/B tests. Expose changes to some users while showing others the unchanged, original
experience. Based on how users engage with the experiences, you
can determine if you want to roll the changes out to the rest of
the users, or if the original experience performs better.
Uniform gives you the ability to create and control all aspects
of A/B tests so you can iterate faster during your digital
production process.
## How A/B testing works
Uniform implements A/B testing through an **A/B test** component that you place within a composition. This component contains multiple variations that can be displayed to visitors. Each variation can be assigned a specific _distribution percentage_, which determines what portion of your audience will see that particular variation.
To select a test variation, Uniform generates a random number between 0 and 100. This random number determines which variation is shown.
For example:
| Variation | Distribution | Number range |
| --- | --- | --- |
| Variation A | 50% | 0 - 50 |
| Variation B | 40% | 50 - 90 |
| Variation C | 10% | 90 - 100 |
Uniform matches the random number with the corresponding range for the variation. If the number generated was **40**, the visitor would see **Variation A**.
### Document your hypothesis
Each **A/B test** component includes a **Hypothesis** field where you can document the reasoning behind your experiment. Use this field to record:
- What you expect to learn from the test
- Why you believe one variation might perform better than another
- The business goal or metric you're trying to improve
Documenting your hypothesis helps with team communication and experiment governance. It also provides context when reviewing test results later.
> **AI-assisted variation creation:**
>
> When you use [Scout](https://docs.uniform.app/docs/guides/ai/scout) to help create test variations, Scout reads the hypothesis field to understand the purpose of your test and generates more relevant content suggestions.
### Measuring effectiveness
Any effective testing strategy must be measured to make sure it's having a positive effect. To enable this, Uniform enables you to connect its test results to any analytics tool available. Each **A/B Test** component has a _name_ which is sent to any connected analytics along with the variation that was selected. The resulting data can then be analyzed and reported on in any way the analytics tool allows.
Inside of the Uniform Testing dashboard, you are able to connect the Google Analytics integration and view reporting associated with the test.
Uniform ships with a connector for Google Analytics v4 (gtag), and a generic event-handling interface that adapts to any tool with minimal code.
### Choosing a winner
Once a test has been completed, a winning variation is able to be declared using the Uniform Testing dashboard. Once a winner is declared and has been republished in the dashboard, only the winning variation will be shown to every visitor on the site even if they’ve previously seen a different variation in the past.
Completed tests should periodically be removed with the winning variation directly to avoid building up a large amount of completed tests across the site.
## Activate A/B testing
If you are using Uniform Canvas, A/B testing is handled
automatically. However, if you aren't using Canvas, you can
still take advantage of testing, you just have to
add it to your front-end application yourself.
The following example tests a component.
> **Info:**
>
> This code requires the following:
>
> 1. The Uniform tracker is [added to the front-end application](https://docs.uniform.app/docs/guides/classification/programmatic-classification#add-the-tracker).
> 2. Manifest has an A/B test with the id `dxcpTest`.
**React.js**
```jsx
import { Test } from '@uniformdev/context-react';
const variations = [
{ text: 'Digital Experience Composition Platforms (DXCP) help business users and developers collaborate better.' },
{ text: 'Business users need better tools to collaborate with developers.' },
{ text: 'Developers can work smarter when business users have the proper tools.' },
];
export function DxcpTest() {
return (
);
}
function ContentBlock({ text }) {
return (
{ text }
);
}
```
### Handle tracker events
You can define event handlers for the events that are emitted from the Uniform tracker during the testing process.
#### Test result
## Manage A/B testing in Uniform
### Create test
1. In Uniform, navigate to the **Optimization > Testing** tab.
2. Click the red **(+)** button.
3. Enter the following values:
| Field | Description |
| --- | --- |
| Name | Name that describes the test. |
| Public ID | Name that uniquely identifies the test. This value is available to developers. |
4. Click **Create**.
> **Note:**
>
> A test involves Uniform automatically selecting one component
> in a slot to be displayed. Testing must be enabled on the slot
> with the components you want to test.
### Enable testing on slot
> **Before you start:**
>
> Before you can test a component, you must have a component defined.
> For information on how to define a component, see the [components guide](https://docs.uniform.app/docs/guides/models/components).
1. In Uniform, navigate to a component with a slot that you want to test.
2. Click the component.
3. Select the **slot** tab and select the desired slot.
4. In the section **Allowed Components**, select the component **A/B Test**. You can search or find it at the bottom of the list of components.
> **Note:**
>
> You must have other component types selected on the slot. Those
> will be the component types that can be tested in this slot.
5. Click **OK**. Be sure to **save and close** the component.
> **Info:**
>
> Next you must configure a test on a component.
### Configure test on component
1. In Canvas, open a composition with a component you want to test.
2. Select the component you want to test.
3. Click the **Context** tab in the property panel and select **A/B Test This**.
If this button isn't available, you probably didn't complete the section where you [enable testing on a slot](#enable-testing-on-slot).
> **Note:**
>
> When you click the button **A/B Test This**, a new component
> **A/B Test** is inserted as the parent of the component you
> have selected. You use this component to configure how the
> test affects the component you selected.
4. Add additional components under the test component.
> **Note:**
>
> In order for a test to do anything, there must be at least
> two components under the test component. These are called
> "test variations."
>
> When you add additional components, new fields appear in the property panel to configure the test:
>
> | Field | Description |
> | --- | --- |
> | Variation name | Label that describes this variation. It's used in reporting. |
> | Visitor Distribution | By default (no value specified), all variations have an equal chance of being displayed. You can set this value to make this variation more or less likely to be displayed. |
5. Save the composition.
6. You must publish your composition before the A/B test you've configured is available to the front-end.
> **Tip:**
>
> A/B testing is already integrated into Canvas, so there are
> no front-end code changes you need to make. After you publish
> your composition, test content should be available right away.
## Measuring your test
[Uniform Insights](https://docs.uniform.app/docs/guides/insights) shows per-variation performance in an **Insights** tab on the test component itself, and detects a winning variation once the data supports one.
See [test and personalization insights](https://docs.uniform.app/docs/guides/insights/test-and-personalization-insights) for how to read the results, and [measure conversions](https://docs.uniform.app/docs/guides/insights/measure-conversions) for how to define what counts as a conversion.