Test selection

Yellow Jacket can execute a subset of configured routes and scenarios.

Select a route

Routes can be selected by their configured name:

yellow-jacket run --route health

or by their path:

yellow-jacket run --route /health

The option can be repeated:

yellow-jacket run \
  --route health \
  --route users

Select a scenario

Select a complete scenario by name:

yellow-jacket run --scenario checkout

A selected scenario always runs from its first step.

Yellow Jacket does not select individual scenario steps because later steps can depend on variables captured by earlier steps.

Tags

Routes and scenarios can declare tags:

export default defineConfig({
  baseUrl: 'http://localhost:3000',

  routes: [
    {
      name: 'health',
      path: '/health',
      tags: ['smoke']
    }
  ],

  scenarios: [
    {
      name: 'checkout',
      tags: ['smoke', 'commerce'],

      steps: [
        {
          name: 'create cart',
          method: 'POST',
          path: '/cart'
        }
      ]
    }
  ]
});

Run all matching targets:

yellow-jacket run --tag smoke

Combining selectors

Different selectors form a union.

For example:

yellow-jacket run \
  --route health \
  --scenario checkout \
  --tag critical

runs every target matching any of those selectors.

If nothing matches, Yellow Jacket exits with code 2.

Baselines

Selectors are supported directly by run.

For baseline management, selectors are supported only together with --update. A command such as:

yellow-jacket baseline --tag smoke

is rejected because replacing the complete baseline with a partial snapshot would discard unselected responses.

During a filtered run, Yellow Jacket filters the existing baseline to the selected routes and scenarios before comparison. Unselected baseline entries are therefore not reported as missing.

Updating selected baseline entries

A normal baseline command always replaces the complete baseline:

yellow-jacket baseline

Yellow Jacket therefore rejects selectors on a normal baseline command.

To intentionally refresh only part of an existing baseline, use --update:

yellow-jacket baseline \
  --update \
  --route health

The same mode works with scenarios and tags:

yellow-jacket baseline \
  --update \
  --scenario checkout

yellow-jacket baseline \
  --update \
  --tag smoke

Partial updates preserve every unselected snapshot.

Selected snapshots are replaced by their new response, while newly selected routes that were not already present are appended to the baseline.

--update requires an existing baseline. If no baseline exists yet, create the complete one first:

yellow-jacket baseline

Route expectations must still pass before any baseline file is modified.