Metadata fields

You can use Metadata fields to attach custom attributes to individual test runs inside your Playwright projects. These attributes are fully customisable and appear in the details pane of each test run within your dashboard. It supports a wide variety of data types so you can capture anything from environments to test owners to impacted components. Here's the full list:

• Textual: Text, Textarea, Email, Phone number.

• Numerical: Number, Integer, Decimal.

• Choice-based: Single Option, Multi Option, Checkbox.

• Temporal: Date, Time, Date Range, Time Range, Date & Time.

• Validation-based: RegExp.

This means you can capture anything from priority = high, component = booking, env = staging, to owner = Deepanshu.

How it works?

1. Set up metadata fields in project settings:

Navigate to your project settings and configure the metadata fields. Choose field names and types. All fields are optional — they can be left blank in the test run metadata. You can also reorder the fields, and the order you set in the settings page will be reflected in the metadata dropdown of each test.

2. Fill metadata per test run:

Once fields are configured, users can fill in metadata per test run directly from the test details pane in the dashboard. This ensures consistent tagging across teams.

Use Cases:

Environment-Specific Failures

• Tag tests with env = staging or env = prod

• Compare flakiness across different environments

Test Type & Priority

• Use test_type = smoke and priority = high

• Quickly locate critical failures in nightly pipelines

Regression Patterns

• Use date/time fields to mark known regression windows

• Filter tests that failed during a specific release window

FAQs?

How RegExp field type works?

First, select the field type RegExp while creating a metadata field in your project settings. Then, provide the regular expression pattern that the input value must match. You can also add a Help Message to guide users on the expected format. This field will only accept values that match the provided RegExp, ensuring that data entered by users is always in a consistent, validated format.

If a user enters a value that does not match the pattern, the system will prevent submission and display the help message as a validation error.

Example:

• Field Label: Ticket ID

• RegExp Pattern: ^TICKET-\d{4}$

• Help Message: Format should be like TICKET-1234

Using this field, you can:

• Enforce structured data entry, like BUG-####, FEAT-####, or PRD-YYYY-MM-DD .

• Link tests to Jira ticket IDs, GitHub issue IDs, or release versions.

• Capture test case IDs with a consistent naming convention.

• Validate custom URL patterns, browser version formats, or semantic versioning.

• Prevent human error or inconsistent formatting when metadata is user-supplied.