Common Recipes

Copy-paste patterns for common workflows.

CI with machine-readable output

glubean ci run

Use profiles.ci.reporters in glubean.yaml to write both a Glubean result file and JUnit XML for CI dashboards. glubean ci run runs the ci profile from glubean.yaml; fail-fast and reporter paths come from profiles.ci. See Connect CI and Configuration.

Switch environments without changing code

glubean run                              # default (.env)
glubean run --env-file .env.staging
glubean run --env-file .env.prod

The CLI auto-pairs each env file with its .secrets counterpart. See Environments & Secrets.

Map shell variables to test names

export GLUBEAN_URL=https://api.example.com
export GLUBEAN_API_KEY=your_api_key_from_secret_store
 
printf "BASE_URL=\${GLUBEAN_URL}\n" > .env
printf "API_KEY=\${GLUBEAN_API_KEY}\n" > .env.secrets
 
glubean run

Run by tags

glubean run --tag smoke
glubean run --tag smoke --tag auth --tag-mode and

Run and upload to Cloud

glubean run --profile local --upload --project <id>

Or run the ci profile and upload in one step:

glubean ci run --upload --project <id>

Sync source projections to Cloud

glubean sync --project <id>

sync does not execute code. It publishes source-derived Specifications, OpenAPI-shaped projections, and agent/spec context. See Sync Projections.

Run load evidence

glubean load tests/load/shop.load.ts
glubean load tests/load/ --upload --upload-target tgt_abc

Load plans do not use glubean.yaml profiles; put the exact command in package.json or CI when you want a repeatable load workflow.

Preview redaction before upload

glubean redact --input .glubean/last-run.result.json

See Redaction & Privacy for details.