# clanker run

Run the project's Playwright specs and publish the run to the workspace

## Usage

```bash
clanker run [options] [playwrightArgs...]
```

## Arguments

- `<playwrightArgs>` (optional): Extra Playwright arguments

## Options

- `--environment <environment>`: Environment to test; its deployment of the product supplies the URL. Required to publish
- `--product <product>`: Product to test (default: the product in clanker.json)
- `--base-url <url>`: Test this URL instead of the deployment's
- `--fixture-url <url>`: Make test data through this Fixture API instead of the deployment's
- `--keep-data`: Keep the run's test data until its scope expires (not on production)
- `--workspace <slug>`: Workspace slug or id (default: the linked workspace)
- `--coverage <level>`: Cumulative coverage: critical, acceptance, regression, or exhaustive
- `--id <id>`: Case ID to include (repeatable)
- `--folder <folder>`: Case folder to include (repeatable)
- `--workers <count>`: Tests to run at once: a number, or a percentage of CPU cores such as 100% (default: the Playwright config)
- `--shard <shard>`: Run this machine's share of the specs, such as 2/4
- `--run-key <key>`: The key every shard of one run passes, so they publish one run, such as github-<run id>-<attempt>
- `--ui`: Open the Playwright UI
- `--no-publish`: Run the specs without publishing the run

## Examples

```bash
clanker run --environment staging
clanker run --environment staging --coverage critical
clanker run --no-publish --base-url http://127.0.0.1:3000
```