Set up Datadog Synthetic browser test on a private location with schedule and CI trigger

Steps

1. Deploy the Datadog private location worker by pulling the datadog/synthetics-private-location-worker Docker image and running it with the private location configuration JSON (obtained from the Datadog UI under Synthetics > Settings > Private Locations); the worker registers itself and begins polling for test assignments.
2. Create a browser test via POST /api/v2/synthetics/tests with type 'browser'; reference the private location's ID in the locations array; include the start_url, name, tags, and options.device_ids fields to specify browser viewport and user agent.
3. Record the browser test steps using the Datadog browser test recorder in the UI (a Chrome extension) and save the recorded steps; the API can update an existing test's steps via PUT /api/v2/synthetics/tests/{public_id} with the recorded step definitions in the config.steps array.
4. Set the scheduling via options.tick_every (interval in seconds); for CI/CD on-demand execution use the Datadog CI integration: install @datadog/datadog-ci and run datadog-ci synthetics run-tests --public-id <id> from the pipeline with DD_API_KEY and DD_APP_KEY environment variables set.
5. Configure assertions on the browser test such as asserting the presence of specific page elements, text content, or URL patterns after key actions; assertions are defined in the steps as 'assertElementContent' or 'assertCurrentUrl' step types.
6. Review test results in the Datadog Synthetics UI under the test's timeline view; failures include a screenshot at the point of failure and the full DOM snapshot to accelerate debugging; long-running tests (over a few minutes) should be broken into shorter focused tests.