Skip to content

Commit 1281565

Browse files
author
George Haberis
committed
updated ReadMe copy
1 parent c80ee0c commit 1281565

File tree

1 file changed

+18
-16
lines changed

1 file changed

+18
-16
lines changed

dotcom-rendering/docs/development/ab-testing-in-dcr.md

Lines changed: 18 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -209,19 +209,7 @@ const someComponent = () => {
209209

210210
```
211211

212-
#### Testing your changes on CODE
213-
214-
If you want to test your changes on CODE you need to follow these steps:
215-
216-
1. Configure the A/B tests on your branch
217-
218-
2. Deploy your branch to CODE
219-
220-
3. Manually run the [🧪 AB testing CI (CODE)](https://github.com/guardian/dotcom-rendering/actions/workflows/ab-testing-ci-code.yml) worfklow using your branch. This deploys the test config to Fastly CODE.
221-
222-
The 3rd step is crucial as Fastly buckets users into tests/cohorts and returns your A/B test participations as response headers.
223-
224-
#### Ways to check your participation
212+
### Ways to check your participation
225213

226214
#### In source code
227215

@@ -259,7 +247,19 @@ Server side tests are also available in the CAPI object e.g. `CAPIArticle.config
259247

260248
Fastly sends a user's AB participations via the `x-gu-server-ab-tests` response header (server side A/B tests) and `gu_client_ab_tests` response cookie (client side A/B tests).
261249

262-
#### Forcing yourself into a test on PROD
250+
### Testing your changes on CODE
251+
252+
If you want to test your changes on CODE you need to follow these steps:
253+
254+
1. Configure the A/B tests on your branch
255+
256+
2. Deploy your branch to CODE
257+
258+
3. Manually run the [🧪 AB testing CI (CODE)](https://github.com/guardian/dotcom-rendering/actions/workflows/ab-testing-ci-code.yml) worfklow using your branch. This deploys the test config to Fastly CODE.
259+
260+
The 3rd step is crucial as Fastly buckets users into tests/cohorts and returns your A/B test participations as response headers.
261+
262+
### Forcing yourself into a test on PROD/CODE
263263

264264
Use the opt-in and opt-out URL fragments to force yourself into or out of a test.
265265

@@ -269,5 +269,7 @@ When opted-out, you'll return to random/mvt based assignment.
269269

270270
These links are also in the [frontend admin](https://frontend.gutools.co.uk/analytics/ab-testing).
271271

272-
- Opt-in Example: `https://theguardian.com/ab-tests/opt/in/commercial-test-example:variant`
273-
- Opt-out: `https://theguardian.com/ab-tests/opt/out`
272+
- Opt-in Example on PROD: `https://theguardian.com/ab-tests/opt/in/commercial-test-example:variant`
273+
- Opt-out on PROD: `https://theguardian.com/ab-tests/opt/out`
274+
275+
You can use the same routes on CODE.

0 commit comments

Comments
 (0)