testeiya 0.2.1 → 0.3.10

package/skills/testeiya/testomatio-docs/docs/advanced/tql/index.md

@@ -1,394 +0,0 @@
----
-title: Query Language
-description: Explore how to filter and retrieve test data using Testomat.io Query Language (TQL). This guide explains the use of basic selection operators like and, or, not, and introduces variables such as tags, labels, priorities, and dates. Learn how to write complex queries to efficiently manage test suites and filter tests based on various criteria, enhancing test tracking and organization.
-type: article
-url: https://docs.testomat.io/advanced/tql
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/image-10.CseiEB5H_m3LwE.webp
-
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, query language, TQL, test filtering, test management, test queries, variables, priority filter, tag filter, automation, QA tools, testing efficiency
----
-
-TQL or **Testomat.io Query Language** is a flexible way to filter tests data inside Testomat.io. Query Language provides basic selection operators like **and**, **or** and **not** and **braces** to prioritize selection.
-
-## Writing Queries
-
-To access Query Language Editor click on the button right to search field on Tests screen:
-
-![TQL Access](./images/tql_in_1.png)
-
-This will open an extended TQL editor which allows to write queries in a dedicated interface with some hints provided:
-
-![TQL Access](./images/tql_in_2.png)
-
-:::note
-
-Alternatively, enter `=` in the Search field at the beginning of your query.
-
-:::
-
-A query can select tests by comparing its fields. The basic comparison operators are: `==` for 'equals' and `!=` for 'not equals'.
-
-The most popular use case would be selecting tests by tag A or by tag B.
-
-This could be written as following query:
-
-```ruby
-tag == 'A' or tag == 'B'
-```
-
-if a test needs to have both tags at once, use `and` operator:
-
-```ruby
-tag == 'A' and tag == 'B'
-```
-
-In case you want tests with tag A excluding tests that contain tag B, this should be the query:
-
-```ruby
-tag == 'A' and not (tag == 'B')
-```
-
-or the same with `!=`
-
-```ruby
-tag == 'A' and tag != 'B'
-```
-
-In case you build a complex query use braces `()` to explicitly set priority of comparison. For instance, to select tests with tag A or tests with both tags B and C, use braces to set priority:
-
-```ruby
-tag == 'A' or (tag == 'B' and tag == 'C')
-```
-
-<Aside type="caution" title="Important">
-
-**Use braces** when you have combination of `and` / `or` operators. Query like `A and B or C and D` is ambiguous, so it should be rewritten to something like: `(A and B) or (C and D)` to explicitly set the order of operators.
-
-</Aside>
-
-Please note, that most of variables requires values in string format wrapped into single or double quotes:
-
-```
-tag == A <- won't work !!!
-
-tag == 'A' <- will work
-```
-
-Also, the equality should always be set as `==`:
-
-```
-tag = 'A' <- won't work !!!!
-
-tag == 'A' <- will work
-```
-
-### Multiple values
-
-It may be necessary to find multiple values associated with a single variable. Fortunately, TQL provides a straightforward solution.
-
-The `in` operator in Testomat.io Query Language (TQL) is a powerful tool designed to simplify complex filtering. Instead of chaining multiple `or` conditions, you can use `in` to check if a field's value matches any item in a specified list. This makes your queries significantly more readable and maintainable.
-
-**The Syntax**
-The basic structure requires the variable name followed by the `in` operator and a comma-separated list of values wrapped in square brackets `[]` and single quotes `'`.
-
-- **Brackets:** Use square brackets `[]` to define the list of values.
-- **Quotes:** Always wrap string values in single quotes `'value'`.
-- **Equality:** When filtering for a single value alongside an `in` operator (complex examples added below), always use `==` for equality.
-- **Variable Names:** Ensure you use the correct system names (e.g., `created_by` instead of `created`, `state` for automation status).
-- **Case Sensitivity:** TQL typically respects the case of your tags and labels, so ensure they match your project settings.
-
-![Testomat.io - TQL Multiple values](./images/tql_in_3.png)
-
-#### Examples
-
-```ruby
-# list tests with smoke, regression, or sanity tags
-tag in ['smoke', 'regression', 'sanity']
-
-# filter tests by specific high priority levels
-priority in ['critical', 'important']
-
-# find tests that resulted in failed, skipped, or passed status
-status in ['failed', 'skipped', 'passed']
-
-# filter tests belonging to specific functional suites
-suite in ['Payments', 'Checkout', 'Cart']
-
-# list tests linked to a specific set of Jira issues
-jira in ['JST-1', 'JST-2', 'JST-3']
-
-# filter tests by multiple custom labels or severity levels
-label in ['Severity:⚠️ Critical', 'Automatable', 'Post-Deploy']
-```
-**Advanced Combinations**
-
-The `in` operator becomes even more effective when combined with other TQL operators like `and` or `not`.
-
-```ruby
-# Negative Filtering: list all sanity tests that are NOT assigned to specific team members
-tag == 'sanity' and not assigned_to in ['John Doe', 'Jane Smith']
-
-# Complex Scoping: select automated tests in specific modules with critical priority
-state == 'automated' and suite in ['API', 'Database'] and priority == 'critical'
-
-# combined: find recent updates made by specific owners
-created_by in ['Les Kurbas', 'Olena Pchilka'] and updated_at >= 1.week_ago
-```
-:::note
-
-Using `in` is much more efficient than using multiple `or` statements. For instance:
-
-**Inefficient:** `tag = 'v1' or tag = 'v2' or tag = 'v3'`
-
-**TQL Standard:** `tag in ('v1', 'v2', 'v3')`
-
-By using the `in` operator, you reduce the risk of syntax errors (like missing a variable name in a long `or` chain) and make the query much easier for other team members to understand at a glance.
-
-:::
-
-## Tests Variables
-
-In previous section we used `tag` in the query. `tag` is an allowed query variable. Here is a comprehenisve list of variables you can use in the query:
-
-| Variable      | Description                                   | Example                                                                                                                  |
-| ------------- | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
-| tag           | Match tests by tag                            | `tag == 'important'`                                                                                                     |
-| label         | Match tests by label or custom field          | `label == 'Automatable'`                                                                                                 |
-|               |                                               | `label == 'Severity:🔥Critical'` (please note that you need to include emojis if you use them as value in custom fields) |
-| priority      | Match tests by priority                       | `priority >= 'normal'`                                                                                                   |
-|               |                                               | `priority == 'critical'`                                                                                                 |
-| issue         | Match tests by issue as URL or Jira issue key | `issue == 'https://github.com/o/r/issues/1'`                                                                             |
-|               |                                               | `issue == 'JST-2'`                                                                                                       |
-| jira          | Match tests by Jira issue key                 | `jira == 'JST-2'`                                                                                                        |
-| state         | Match tests by automation state               | `state == 'automated'`                                                                                                   |
-|               |                                               | `state == 'manual'`                                                                                                      |
-|               |                                               | `state == 'sync'`                                                                                                        |
-|               |                                               | `state == 'unsync'`                                                                                                      |
-| status        | Match tests by run status                     | `status == 'passed'`                                                                                                     |
-|               |                                               | `status == 'failed'`                                                                                                     |
-| custom_status | Match tests by custom status                  | `custom_status == 'Known issue'`                                                                                         |
-|               |                                               | `custom_status IN [‘Expected error’ , ‘Known issue’]`                                                                    |
-|               |                                               | `custom_status % 'issue' `                                                                                               |
-| created_at    | Match tests by creation date                  | `created_at >= 3.days_ago`                                                                                               |
-|               |                                               | `created_at < 1.month_ago`                                                                                               |
-|               |                                               | `created_at == today()`                                                                                                  |
-|               |                                               | `created_at <= '2023-12-31'`                                                                                             |
-| updated_at    | Match tests by last update                    | `updated_at >= 3.days_ago`                                                                                               |
-|               |                                               | `updated_at <= '2023-12-31'`                                                                                             |
-| last_run_at   | Match tests by last execution date            | `last_run_at < 1.week_ago`                                                                                               |
-|               |                                               | `last_run_at == today()`                                                                                                 |
-| executed_at   | Match tests by execution date                 | `executed_at < 1.week_ago`                                                                                               |
-|               |                                               | `executed_at == today()`                                                                                                 |
-| created_by    | Match tests by author's name                  | `created_by == 'Antonio Primus'`                                                                                         |
-| assigned_to   | Match tests by assignee's name                | `assigned_to == 'Antonio Primus'`                                                                                        |
-| suite         | Match tests inside a folder or suite          | `suite % 'Checkout'`                                                                                                     |
-|               |                                               | `suite == '{SUITE_ID}'`                                                                                                  |
-| test          | Match tests by title or ID                    | `test % 'User login'`                                                                                                    |
-|               |                                               | `test == '{TEST_ID}'`|
-| milestone          | Match tests by milestone title                    | `milestone == 'Milestone-name'` |
-| | | `milestone != 'Milestone-name'` |
-| | | `milestone in ['Milestone-A', 'Milestone-B']` |
-
-#### Examples
-
-```ruby
-# list tests linked to specific jira issues
-jira in ['JST-1', 'JST-2', 'JST-3']
-
-# failed tests with either smoke or stage1 tag
-tag in ['smoke', 'stage1'] and status == 'failed'
-
-# list important and automatable tests by label
-label == 'Automatable' and priority > 'normal'
-
-# list recently created tests
-created_at < 1.month_ago
-
-# list of tests with a label in selected suites
-(suite % 'suite title 1' or  suite % 'suite title 2') and  label == 'Automatable'
-
-# tests that were last executed today
-last_run_at == today()
-
-# tests executed in July 2025 with failed status
-executed_at >= '2025-07-01' and executed_at <= '2025-07-31' and status == 'failed'
-```
-
-## Runs Variables
-
-Testomat.io has implemented a Query Language for Runs to make the search more flexible. You are already familiar with some of the variables from the previous section, but more new features have been implemented for Runs, which gives you new opportunities.
-
-Before diving into the details of variables, it's important to understand that variables starting with `has_` are used to filter **test runs** by whether they match certain **test criteria**. Specifically:
-
-- `has_test`: This variable allows you to filter runs based on whether they contain specific tests, which are identified by their title or ID. In other words, you can use `has_test` to find test runs that include tests that match a given name or ID.
-
-| Variable          | Description                                                          | Example                                                       |
-| ----------------- | -------------------------------------------------------------------- | ------------------------------------------------------------- |
-| title             | Match runs by title                                                  | `title == 'Run title'`                                        |
-|                   |                                                                      | `title % 'Manual tests'`                                      |
-| plan              | Match runs by plan                                                   | `plan == '{PLAN_ID}'`                                         |
-|                   |                                                                      | `plan % 'Smoke tests'`                                        |
-| rungroup          | Match runs by rungroup title                                         | `rungroup == '{RUNGROUP_ID}'`                                 |
-|                   |                                                                      | `rungroup % 'Rungroup Title'`                                 |
-| env               | Match runs by environment                                            | `env == 'Production'`                                         |
-|                   |                                                                      | `env IN ['Windows', 'Linux']`                                 |
-| tag               | Match runs by tag                                                    | `tag == 'slow'`                                               |
-| label             | Match runs by label or custom field                                  | `label IN ['Severity:🔥Critical', 'Automatable']`             |
-| jira              | Match runs by jira_id or Jira issue key                              | `jira == 'JST-1'`                                             |
-| duration          | Match runs by duration in seconds                                    | `duration < 1000`                                             |
-| passed_count      | Match runs by number of passed tests                                 | `passed_count > 100`                                          |
-| failed_count      | Match runs by number of failed tests                                 | `failed_count < 10`                                           |
-| skipped_count     | Match runs by number of skipped tests                                | `skipped_count < 10`                                          |
-| automated         | Match runs by automated                                              | `automated`                                                   |
-| manual            | Match runs by manual                                                 | `manual`                                                      |
-| mixed             | Match runs by mixed                                                  | `mixed`                                                       |
-| finished          | Match runs by finished                                               | `finished`                                                    |
-| unfinished        | Match runs by unfinished                                             | `unfinished`                                                  |
-| passed            | Match runs by passed status                                          | `passed`                                                      |
-| failed            | Match runs by failed status                                          | `failed`                                                      |
-| terminated        | Match runs by terminated                                             | `terminated`                                                  |
-| published         | Match runs by published                                              | `published`                                                   |
-| private           | Match runs by private                                                | `private`                                                     |
-| archived          | Match runs by archived                                               | `archived`                                                    |
-| unarchived        | Match runs by unarchived                                             | `unarchived`                                                  |
-| with_defect       | Match runs that have linked defects                                  | `with_defect`                                                 |
-| has_defect        | Match runs containing tests with linked defect by defect title or ID | `has_defect IN [‘TST-1’ , ‘github.com#123123’]`               |
-|                   |                                                                      | `has_defect == ‘{JIRA_ID}’`                                   |
-| has_test          | Match runs containing tests by their title or ID                     | `has_test == '{TEST_ID}'`                                     |
-|                   |                                                                      | `has_test % 'Important test'`                                 |
-| has_test_tag      | Match runs containing tests with specific tags                       | `has_test_tag == 'regression'`                                |
-| has_test_label    | Match runs containing tests with specific labels                     | `has_test_label == 'Automatable'`                             |
-| has_suite         | Match runs containing suites by their title or ID                    | `has_suite % 'Users'`                                         |
-| has_message       | Match runs containing tests with messages                            | `has_message == "Result message"`                             |
-| has_custom_status | Match runs containing tests with custom status                       | `has_custom_status IN [‘Expected behaviour’ , ‘Known issue’]` |
-|                   |                                                                      | `has_custom_status == ‘Expected behaviour’`                   |
-| has_assigned_to   | Match runs containing tests assigned to specific users               | `has_assigned_to IN ['John Doe', 'Jane Smith']`               |
-| has_retries       | Match runs containing tests with retries                             | `has_retries > 2`                                             |
-| has_test_duration | Match runs containing tests with specific durations                  | `has_test_duration <= 1.minute`                               |
-| has_priority      | Match runs containing tests with specific priority                   | `has_priority in ['low', 'critical']`                         |
-|                   |                                                                      | `has_priority == 'important'`                                 |
-| created_at        | Match runs by creation time                                          | `created_at <= 1.week_ago`                                    |
-| updated_at        | Match runs by last update                                            | `updated_at >= 5.days_ago`                                    |
-| launched_at       | Match runs by launch time                                            | `launched_at > 2.days_ago AND launched_at < 1000.seconds_ago` |
-| finished_at       | Match runs by finish time                                            | `finished_at < 7.days_ago`                                    |
-| milestone          | Match runs by milestone title                    | `milestone == 'Milestone-name'` |
-| | | `milestone != 'Milestone-name'` |
-| | | `milestone in ['Milestone-A', 'Milestone-B']` |
-
-#### Examples
-
-```ruby
-# match failed runs with all User tests
-failed and has_test % 'User'
-
-# match runs with tests from Smoke Tests plan
-finished and plan % 'Smoke Tests'
-
-# match runs with tests with @regression tag
-failed and has_test_tag == 'regression'
-
-# list all runs with tests that have tests as flaky
-finished and finished_at < 1.week_ago and has_test_label == 'Flaky'
-
-# list all runs with tests that have connection errors
-failed and has_message % 'Connection Error'
-
-# list all runs with tests that have retries
-finished and has_retries > 2
-
-# list all runs that contain Jira Issues or Issues linked to tests results
-finished and with_defect
-
-# automated tests executed in production and had Server error in messages
-automated and env == 'Production' and has_message % 'Server Error'
-
-# failed runs finished in July 2025
-finished_at >= '2025-07-01' and finished_at <= '2025-07-31' and failed
-
-# runs that started in July 2025 and finished in August 2025
-launched_at >= '2025-07-01' and launched_at <= '2025-07-31' and finished_at >= '2025-08-01' and finished_at <= '2025-08-31'
-
-```
-
-## Filter By Priority
-
-Priority variable allow additional comparisons operators to be used `>` `<` `>=`, `<=`. So you can select tests with a priority higher than normal:
-
-```ruby
-priority > 'normal'
-```
-
-## Filter By Title
-
-To match test by its title or its suite title a special operator `%` was introduced. This allows to match all tests containing a text inside its title. For instance, this query will match all tests with word `User` in their title:
-
-```ruby
-# when searching for tests
-test % 'User'
-
-# when searching for runs containing test
-has_test % 'User'
-```
-
-Searched text should be longer than 4 chars.
-
-This also works for suites, so you can select all tests from a suite containing `User` word:
-
-```ruby
-# when searching for tests from a suite
-suite % 'User'
-
-# when searching for runs containing tests from a suite
-has_suite % 'User'
-```
-
-However, if there are multiple suites with word User in their title, **only the first suite will be selected**.
-
-## Dates
-
-When you deal with date variables like `created_at`, `last_run_at`, and others you can set absolute date in `YYYY-MM-DD` format or use functions like `days_ago`, `weeks_ago`, `months_ago` to specify a date from now.
-
-Examples:
-
-```ruby
-1.day_ago
-3.days_ago
-
-
-1.week_ago
-2.weeks_ago
-
-1.month_ago
-5.months_ago
-```
-
-There is also `today()` function that can be used to specify current date. For instance, to list all tests created today use this query:
-
-```ruby
-created_at == today()
-```
-
-To list all tests created for the previous week use `1.week_ago` with `>` operator:
-
-```ruby
-created_at > 1.week_ago
-```
-
-## Users
-
-Variables like `assigned_to` or `created_by` require user names to be passed as value. For instance, this will select all tests created by John Snow.
-
-```ruby
-created_by == 'John Snow'
-
-created_by IN ['John Snow', 'John Doe']
-```
-
-Filtering always happens by user name, not by email or user ID. Also, user should exist inside the project.