Deployment tags

Deployment tags declare where a test suite is expected to run. Add them to every test.describe() (or apiTest.describe() / spaceTest.describe()), then use --grep when running tests to target a specific environment.

Tags follow this shape:

• @<location>-<arch>-<domain>

Where:

• location: local or cloud
• arch: stateful or serverless
• domain: classic, search, observability_complete, security_complete, …

Use the tags helper (see the full list below) to declare where your tests should run. By default, each helper expands to both @local-* and @cloud-* targets:

test.describe(
  'My suite',
  { tag: [...tags.stateful.classic, ...tags.serverless.security.complete] },
  () => {
    // ...
  }
);
		

This is equivalent to assigning all of these tags:

• @local-stateful-* (local stateful)
• @cloud-stateful-* (Elastic Cloud)
• @local-serverless-security_complete (local serverless)
• @cloud-serverless-security_complete (Elastic Cloud)

To restrict a test to local environments only, write the tag strings explicitly:

test.describe(
  'My suite',
  { tag: ['@local-stateful-classic', '@local-serverless-security_complete'] },
  () => {
    // ...
  }
);
		

This test will only run locally (stateful classic and serverless Security complete tier), and will be skipped by Elastic Cloud pipelines.

Use this tag for platform specs that need to run across every standard deployment type. It expands to:

• tags.stateful.all
• tags.serverless.search
• tags.serverless.observability.complete
• tags.serverless.security.complete

Workplace AI is excluded because it has no stateful counterpart.

The target solution view indicates the solution view the test is intended for, but is not enforced at test execution time. To set the solution view in a test, use scoutSpace.setSolutionView().

Use tags.performance for performance tests. It assigns the @perf tag.

For the authoritative list (and the exact tag strings), see src/platform/packages/shared/kbn-scout/src/playwright/tags.ts or just rely on editor autocomplete.