# Conditions
An Actions can have one or more condition. You can use `AND` or `OR` combinator for multiple conditions.
### Fields
#### File
Test filename path, for example `path/to/file.spec.ts`.
| Field Type | `string` |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Value Type | `string \| string[] \| RegexPattern[]` |
| Supported Operators | #basic-operators
#one-to-many-operators
|
| Supported Actions | #pre-test-actions
#post-test-actions
|
#### Test Title
Test title, for example in test definition `test("should open landing page")` it is `should open landing page`.
| Field Type | `string` |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Value Type | `string \| string[] \| RegexPattern[]` |
| Supported Operators | #basic-operators
#one-to-many-operators
|
| Supported Actions | #pre-test-actions
#post-test-actions
|
#### Test Title Path
Full title path as an array including named `describe` statements. See [testInfo.titlePath](https://playwright.dev/docs/api/class-testinfo#test-info-title-path). To match the following example:
```json
[
"auth.spec.ts", // e.g. spec file name
"Auth Controller", // e.g. test describe
"Should login with correct credentials" // e.g. test title
]
```
Use a string list: :box:`auth.spec.ts` :box:`Auth Controller` :box:`Should login with correct credentials`
| Field Type | `string[]` |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Value Type | `string \| string[] \| RegexPattern[]` |
| Supported Operators | #basic-operators
#many-to-many-operators
|
| Supported Actions | #pre-test-actions
#post-test-actions
|
#### Test ID
Playwright [test id](https://playwright.dev/docs/api/class-testinfo#test-info-test-id), matching the test case id in the [Reporter API](https://playwright.dev/docs/api/class-reporter).
| Field Type | `string` |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Value Type | `string \| string[]` |
| Supported Operators | #basic-operators
#one-to-many-operators
|
| Supported Actions | #pre-test-actions
#post-test-actions
|
#### Tags
Test tag list. For example, if a test has the following list of tags `['a', 'b']`, each value in the list will be evaluated separately.
| Field Type | `string[]` |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Value Type | `string \| string[]` |
| Supported Operators | #basic-operators
#many-to-many-operators
|
| Supported Actions | #pre-test-actions
#post-test-actions
|
#### Project
Playwright project name as defined in your `playwright.config.ts`.
| Field Type | `string` |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Value Type | `string \| string[] \| RegexPattern[]` |
| Supported Operators | #basic-operators
#one-to-many-operators
|
| Supported Actions | #pre-test-actions
#post-test-actions
|
#### Error Message
{% hint style="info" %}
Added in `@currents/playwright@1.14.0`
{% endhint %}
Used to match a list field (eg Test Title Path) against one or more values.
Error message thrown during the test.
| Field Type | `string` |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Value Type | `string \| string[] \| RegexPattern[]` |
| Supported Operators | #basic-operators
#one-to-many-operators
|
| Supported Actions | [#post-test-actions](https://docs.currents.dev/guides/currents-actions/actions#post-test-actions "mention") |
#### Git Author Email
Git commit author email. See [commit-information](https://docs.currents.dev/dashboard/runs/commit-information "mention") to explore how Currents collects git commit information.
| Field Type | `string` |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Value Type | `string \| string[] \| RegexPattern[]` |
| Supported Operators | #basic-operators
#one-to-many-operators
|
| Supported Actions | #pre-test-actions
#post-test-actions
|
#### Git Author Branch
Git commit author name. See [commit-information](https://docs.currents.dev/dashboard/runs/commit-information "mention") to explore how Currents collects git commit information.
| Field Type | `string` |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Value Type | `string \| string[] \| RegexPattern[]` |
| Supported Operators | #basic-operators
#one-to-many-operators
|
| Supported Actions | #pre-test-actions
#post-test-actions
|
#### Git Branch
Git commit branch name. See [commit-information](https://docs.currents.dev/dashboard/runs/commit-information "mention") to explore how Currents collects git commit information.
| Field Type | `string` |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Value Type | `string \| string[] \| RegexPattern[]` |
| Supported Operators | #basic-operators
#one-to-many-operators
|
| Supported Actions | #pre-test-actions
#post-test-actions
|
#### Git Message
Git commit message. See [commit-information](https://docs.currents.dev/dashboard/runs/commit-information "mention") to explore how Currents collects git commit information.
| Field Type | `string` |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Value Type | `string \| string[] \| RegexPattern[]` |
| Supported Operators | #basic-operators
#one-to-many-operators
|
| Supported Actions | #pre-test-actions
#post-test-actions
|
#### Git Remote Origin
Git remote origin URL. See [commit-information](https://docs.currents.dev/dashboard/runs/commit-information "mention") to explore how Currents collects git commit information.
| Field Type | `string` |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Value Type | `string \| string[] \| RegexPattern[]` |
| Supported Operators | #basic-operators
#one-to-many-operators
|
| Supported Actions | #pre-test-actions
#post-test-actions
|
### Operators
#### Basic operators
| Operator | Description |
|---|
is | value is equal or RegexPattern matches |
is not | value is different or RegexPattern does not match |
is any | field returns true for JS expression !!value === true |
is empty | field returns false for JS expression !!value === true |
#### One to Many operators
Used to match a single value field (eg Test Title), against a list of values.
| Operator | Description |
|---|
in | one of the values from the list matches |
not in | none of the values in the list match |
#### Many to Many operators
{% hint style="info" %}
Added in `@currents/playwright@1.10.0`
{% endhint %}
Used to match a list field (eg Test Title Path) against one or more values.
| Operator | Description |
|---|
includes | all of the values in the list can be found in the field |
includes some | at least one of the values in the list can be found in the field |
missing | all of the values in the list are missing from the field |
missing any | any of the values in the list is missing from the field |
### Examples
| Field | Operator | Value | Description |
|---|
| Test Id | is | 1234 | id is exact match |
| Git Branch | not in | main,stable | no matches |
| Tags | includes | featureA | tag matches |
| Tags | includes some | featA,featB | at least one tag matches |
| Error Message | is | Int(er|ra)net Error: | Errror Message matches the RegexPattern |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.currents.dev/guides/currents-actions/reference/conditions.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.