You can integrate Usetrace into CircleCI to automatically run your traces as part of your build pipeline.
Example: circle.yml
dependencies:
post:
- wget https://tools.usetrace.com/integration/usetrace-run.sh
test:
override:
# Syntax:
# bash usetrace-run.sh [PROJECT_ID] [BASE_URL] [CAPABILITIES] [TAGS]
- bash usetrace-run.sh \
ZqoynvEbLgAYBRbG2qk6zc0fBG0yYOht \
http://testsite.usetrace.com \
chrome,firefox
Argument | Required | Description |
Project ID | ✅ | Your Usetrace project ID (find it under Preferences). |
Base URL | ✅ | The URL where your traces begin (e.g. staging or test site). |
Capabilities | ✅ | Comma-separated list of browsers: |
Tags | optional | Comma-separated list of tags to run only specific traces. |
Example with tags:
- bash usetrace-run.sh \
ZqoynvEbLgAYBRbG2qk6zc0fBG0yYOht \
http://testsite.usetrace.com \
chrome,firefox \
smoke,regression
Notes
Test results are streamed to your CircleCI build logs.
Build fails automatically if any trace fails.
Store sensitive values (like
PROJECT_ID) as environment variables in CircleCI under Project Settings → Environment Variables.