testeiya 0.2.1 → 0.3.9

package/skills/testeiya/check-tests/SKILL.md

@@ -1,260 +0,0 @@
----
-name: check-tests
-description: Sync Testomat.io test cases with the check-tests CLI. Pull tests to `*.test.md` markdown, push markdown back, import automated test code (Playwright, CodeceptJS, Jest, Cypress, Mocha, Vitest, WebdriverIO), and round-trip `@T`/`@S` IDs. Powers Testeiya's Pull/Push buttons. Use to pull, push, sync, import, or export test cases; add, check, or clean test IDs in source; or debug a failed pull, push, or import.
-license: MIT
-metadata:
-  author: Testomat.io
-  version: 1.0.0
----
-
-# check-tests
-
-The Testomat.io sync CLI. npm package `check-tests`, run with `npx`. Three commands:
-
-- `check-tests pull` — download a project's tests as `*.test.md` files.
-- `check-tests push` — upload local `*.test.md` files, then write assigned `@T`/`@S` IDs back.
-- `check-tests <framework> <glob>` — statically parse automated test code (AST only, no execution) and import it.
-
-This is the exact tool behind Testeiya's Pull/Push buttons (`POST /api/workspace/sync` → `cli/src/check-tests.ts`). Raw calls hit the same files and the same project as the buttons.
-
-## Use cases
-
-- Pull a project's manual tests into local markdown to read or edit them.
-- Push edited or newly written `*.test.md` cases back to the project.
-- Import an automation repo's specs (Playwright, CodeceptJS, Jest, …) into the project.
-- Stamp `@T`/`@S` IDs into markdown or source so files round-trip with the TMS.
-- Pull only selected suites, or push only the files just changed.
-- Check IDs in CI, or clean IDs before a fresh import.
-- Diagnose a pull/push/import that reported success but changed nothing.
-
-## Which tool for which tests
-
-- `*.test.md` markdown and code-based specs → this skill.
-- Gherkin `.feature` files → `check-cucumber` (never run check-tests over `features/`).
-- Test run RESULTS (pass/fail of executed runs) → `@testomatio/reporter`.
-- Unsure of the project kind → `scan-automation-project` first.
-
-## Critical rules
-
-- **A push or import without a token silently does nothing and exits 0.** The output says `API key not provided`, but the exit code is success. Judge success by the output — `Data received at Testomat.io` (and for push, `N files updated.`), never by exit code.
-- **Destructive operations need explicit user confirmation first.** `--purge`/`--unsafe-clean-ids` strip IDs with no server check; `--clean-ids` strips known IDs; push overwrites project content and detaches unmatched tests; pull overwrites local files. Before any: say what changes, get a yes, preflight (`pull --dry-run`, `--no-detached` for a subset, git-commit before ID cleanup).
-- **Never change an existing `id:` in a `*.test.md` file.** The ID is the match key; an edited one makes the next push create a duplicate.
-- **Never write a tag shaped like `@T`/`@S` + 8 alphanumerics** (e.g. `@Ta1b2c3d4`). That pattern is reserved for IDs and corrupts sync.
-- Automated tests pulled as markdown are references, not runnable code — the implementation lives in the automation repo and runs via a CI profile. Do not edit them to change behavior.
-- Never count manual tests by grepping `type: manual`. A block with no `type:` line is manual, and that is the common case.
-- Use only flags documented here or shown by `npx check-tests --help`. Do not invent options.
-
-## How Testeiya wires it
-
-Read this before choosing between the app's built-in sync and a raw call.
-
-### The target directory
-
-Run from the workspace root and pass the dir with `-d` — never guess it. `resolveManualTestsDir(cwd)` decides:
-
-- `.testeiya/manual-tests/` when it exists and holds markdown (a code repo with a pulled overlay).
-- else the workspace root when ≥90% of files are `*.test.md` (a managed project workspace under `~/.testeiya/workspaces/<id>/`).
-- else nothing is loaded yet — only a pull into `.testeiya/manual-tests` makes sense.
-
-### What the buttons run
-
-- Pull: `check-tests pull -d <dir> --force [--export-automated] [--suite-ids …]`.
-- Push: `check-tests push -d <dir> [-f <changed files>]`.
-- Uses the shipped bin, falling back to `npx -y check-tests@latest`, with a 120s timeout.
-- Pushes only files changed since the last sync; background push-on-save pushes only suites that already carry an `@S` ID.
-
-### The `--export-automated` rule
-
-- Testeiya's pull adds `--export-automated` so automated tests come down as markdown references.
-- Except in an automation repo (`hasAutomationConfig`: a playwright/codecept/cypress/wdio/testcafe/nightwatch/cucumber config or dependency) — there the spec files already are the automated tests, so markdown copies would duplicate them.
-- Mirror this rule in raw calls.
-
-### Token resolution
-
-Mirror this order; never ask for a token before exhausting it:
-
-1. The managed session's project token — in a single-project session it is already exported as `TESTOMATIO` (with `TESTOMATIO_URL`, `TESTOMATIO_PROJECT_ID`). Multi-project sessions leave `TESTOMATIO` unset; scope each call to one project's token.
-2. The linked project's API key via the connected account (`.testeiya/testeiya.json` + stored auth).
-3. The folder's own `.env` `TESTOMATIO`. check-tests auto-loads `.env` from its cwd.
-
-### Built-in sync vs raw CLI
-
-- Plain full pull/push of the current workspace → use the Pull/Push buttons (or replicate the invocation above). They handle dir, token, and change tracking.
-- Raw CLI → when you need what the buttons don't expose: `--dry-run`, `--suite-ids`, ID cleanup, `TESTOMATIO_BRANCH`, labels, or a code import.
-- First call in a session uses `npx check-tests@latest …`; later calls can drop `@latest`. Do not install it as a project dependency.
-
-## Commands
-
-### pull — Testomat.io → local markdown
-
-Fetches `GET /api/test_data?with_files=true`, writes files under `-d`, creating dirs and overwriting.
-
-| Flag | Meaning |
-|---|---|
-| `-d, --dir <dir>` | Target dir (default `.`). Always the resolved manual-tests dir |
-| `--dry-run` | Preview created/overwritten files; writes nothing. Use before pulling over local edits |
-| `--force` | Skip git safety checks. Testeiya always passes it for its managed dirs |
-| `--export-automated` | Include automated tests as `type: automated` references. Omit in automation repos |
-| `--suite-ids <ids>` | Pull only these suites, comma-separated: `--suite-ids "@S12345678,@S87654321"` |
-
-Without `--force`, pull refuses to run when: the target is non-empty and not a git repo (`Directory is not empty and git is not initialized`); the git tree is dirty (`Git working tree is not clean`); or `TESTOMATIO` is missing. All exit 1.
-
-### push — local markdown → Testomat.io
-
-Shorthand for `check-tests manual '**/*.test.md' --update-ids`. It imports the markdown, waits for the server, then writes assigned IDs back (`N files updated.`). Expect a successful push to modify your files.
-
-Push-specific flag:
-
-- `-f, --files <files…>` — push only these files or globs (quote globs; paths resolve under `-d`). Prefer this when the changed files are known — e.g. output of `qa-write-test-cases` or `improve-test-cases`.
-
-`--update-ids`/`--sync` are already implied — no need to pass them. Other flags come from [shared import flags](#shared-import-flags).
-
-### framework import — automated code → Testomat.io
-
-Parses test source (AST, no execution) and imports the found tests. Main Testeiya use: pairing an automation repo's specs with the manual cases — see `scan-automation-project` and `qa-e2e-tests-reporting`.
-
-```bash
-TESTOMATIO=<token> npx check-tests playwright "tests/**/*.spec.ts" --typescript --update-ids
-```
-
-- First positional = framework (case-insensitive): `playwright`, `codeceptjs` (alias `codecept`), `cypress` (alias `cypress.io`), `jest`, `vitest`, `mocha`, `jasmine`, `protractor`, `testcafe`, `qunit`, `nightwatch`, `newman`, `gauge`, `manual`, `webdriverio-mocha`. Unknown names fall back to the mocha parser.
-- Second positional = a quoted glob, resolved inside `-d`.
-- Without `TESTOMATIO`, it only lists the found tests and exits 0 — a handy parser dry-run.
-
-Import-specific flags:
-
-| Flag | Meaning |
-|---|---|
-| `--typescript` | `.ts`/`.tsx` sources. Needs `typescript` + `@typescript-eslint/typescript-estree`; the CLI prints the install line and exits 1 if missing |
-| `--update-ids` | Write `@T`/`@S` IDs into titles after import (implies waiting). Auto-disabled when `TESTOMATIO_BRANCH` is set. On large repos, import once without it, then rerun with it |
-| `--partial` | Import only `-d`'s tests into the matching folder without detaching anything outside it. Requires `-d`; equals `-d <dir>` + `TESTOMATIO_PREPEND_DIR=<dir>` |
-| `--require-ids` | CI gate: exit 1 listing every non-skipped test missing an ID |
-| `--no-skipped` | CI gate: exit 1 when skipped/exclusive tests exist |
-| `--test-alias <names>` | Custom test-function names, comma-separated (`myTest,customIt`) |
-| `-p, --plugins <plugins…>` | Extra Babel plugins for exotic syntax |
-| `--no-hooks` | Strip before/after hook code from what's shown in Testomat.io |
-| `--line-numbers` | Prefix code lines with their line numbers |
-| `-g, --generate-file <file>` | Also write a markdown test-summary document |
-| `-u, --url <url>` | GitHub base URL (`…/tree/main`) for source links |
-
-### Shared import flags
-
-Accepted by both `push` and framework import:
-
-| Flag | Meaning |
-|---|---|
-| `-d, --dir <dir>` | Root the glob resolves in (default cwd) |
-| `--sync` | Wait for the server to finish. Skip on very large imports (timeout risk) |
-| `--create` | Create tests/suites for IDs present locally but missing in the project (moved from another project) |
-| `--no-detached` | Don't mark tests absent from this import as detached. Required for any partial/subset import |
-| `--no-empty` | Delete suites left empty after import. Conflicts with `--keep-structure` |
-| `--keep-structure` | Force the local folder structure onto the project instead of preserving the project's |
-| `--exclude <pattern>` | Glob to skip (`"**/node_modules/**"`) |
-| `--force` | Skip git checks; also sends `force` to the import API |
-| `--clean-ids` | **Destructive.** Remove this project's IDs from local files (needs `TESTOMATIO`). Confirm first |
-| `--purge` / `--unsafe-clean-ids` | **Destructive.** Remove all `@T`/`@S`-shaped tags with no server check (no key needed) — may eat near-miss tags. Confirm first, verify titles after |
-
-## Environment variables
-
-Read by the CLI itself; a `.env` in the cwd is auto-loaded.
-
-| Variable | Effect |
-|---|---|
-| `TESTOMATIO` | Project API key (`tstmt_…`). Required for any server call. Already exported in single-project sessions |
-| `TESTOMATIO_URL` | Server base URL (default `https://app.testomat.io`). For self-hosted; Testeiya exports it with the token |
-| `TESTOMATIO_BRANCH` | Import into a branch (matched by id, created if missing). Note: silently disables `--update-ids` |
-| `TESTOMATIO_PREPEND_DIR` | Group imported tests under this folder (letters/digits/`-`/`_` only) |
-| `TESTOMATIO_SUITE` | Import into an existing suite by SID (`1234567`, `S1234567`, or `@S1234567`) |
-| `TESTOMATIO_WORKDIR` | Make file paths relative to this dir before sending (monorepos) |
-| `TESTOMATIO_LABELS` | Comma-separated labels on every imported test; `label:value` supported. Alias `TESTOMATIO_SYNC_LABELS` |
-| `TESTOMATIO_NO_DETACHED` | `.env` default equivalent of `--no-detached` |
-| `DEBUG=testomatio:*` | Verbose logging for a failing run |
-
-## Recipes
-
-Run everything from the workspace root. `$TESTOMATIO`/`$TESTOMATIO_URL` are pre-exported in a single-project session.
-
-```bash
-# Managed project workspace (manual tests at the root)
-npx check-tests@latest pull -d . --force --export-automated
-npx check-tests push -d .
-
-# Code repo with the .testeiya/manual-tests overlay
-npx check-tests pull -d .testeiya/manual-tests --force --export-automated
-npx check-tests push -d .testeiya/manual-tests
-
-# Automation repo (specs ARE the automated tests — no --export-automated)
-npx check-tests pull -d .testeiya/manual-tests --force
-
-# Preview a pull before overwriting local edits
-npx check-tests pull -d .testeiya/manual-tests --dry-run
-
-# Pull only the named suites
-npx check-tests pull -d .testeiya/manual-tests --force --suite-ids "@S12345678,@S87654321"
-
-# Push exactly the files just written, without touching other suites
-npx check-tests push -d .testeiya/manual-tests -f login.test.md checkout.test.md --no-detached
-
-# Import Playwright specs and stamp IDs into the code
-TESTOMATIO=<token> npx check-tests playwright "tests/**/*.spec.ts" --typescript --update-ids
-
-# Import into a branch for review (IDs are not written back on a branch)
-TESTOMATIO_BRANCH=dev TESTOMATIO=<token> npx check-tests codeceptjs "tests/**/*_test.js"
-```
-
-## The `*.test.md` format and ID round-trip
-
-One file is one suite. Metadata lives in HTML comments; titles are headings:
-
-```markdown
-<!-- suite
-id: @S12345678
--->
-
-# Suite Title
-
-<!-- test
-id: @T12345678
-priority: high
--->
-
-## Test Title
-
-Steps and expectations in plain markdown.
-```
-
-- Test keys: `id`, `type` (`manual`/`automated`; absent = manual), `priority` (`normal`/`high`/`low`), `assignee`, `creator`, `tags`, `labels`, `issues`, `shared`.
-- Suite keys: `id`, `emoji`, `tags`, `labels`, `assignee`, `issues`. `tags`/`labels` are comma-separated.
-- Suite `issues` are inherited by every test on push; suite `assignee` only by tests without their own.
-- A new test needs no ID — a bare `<!-- test -->` line is enough; the first push expands it and inserts the `id:`.
-- IDs match by exact title. A title edited between import and ID write-back gets no ID.
-- `type` and `shared` are read-only exports — editing them locally has no effect on push.
-
-## Exit codes and troubleshooting
-
-Exit `0` = success, `1` = any failure (no code 2). A success exit with a failure message in the output is possible — always read the output.
-
-| Symptom | Cause | Fix |
-|---|---|---|
-| `API key not provided` (push/import exits 0!) | No `TESTOMATIO` | Resolve the token per the order above; in multi-project sessions export the right one |
-| `Directory is not empty and git is not initialized` / `Git working tree is not clean` (pull, exit 1) | Pull's git safety check | Commit first, or `--force` for Testeiya's own gitignored cache |
-| `Can't find any tests in this folder` | Wrong `-d`/glob, or an unquoted glob eaten by the shell | Re-resolve the dir; quote the pattern |
-| Push succeeds but a suite is missing | File lacks a valid `<!-- test -->` block before a `##`, or isn't `*.test.md` | Fix the block; pass the file via `-f` |
-| Duplicate tests after push | An `id:` was edited or removed locally | Never touch IDs; use `--clean-ids` only for a deliberate fresh import |
-| `--update-ids is disabled in a branch. Skipping…` | `TESTOMATIO_BRANCH` set | Expected; merge the branch, then rerun `--update-ids` off-branch |
-| `--partial requires -d option` | `--partial` without `-d` | Add `-d <dir>` |
-| `@babel/…` or TypeScript module error (exit 1) | `--typescript`/`--plugins` deps missing | Install what the message names |
-| Import hangs/times out with `--sync` on a big repo | Server-side timeout | Drop `--sync`; import async, then `--update-ids` in a second run |
-| HTTP error `(4xx: …)` | Bad/revoked token or wrong `TESTOMATIO_URL` | Verify the token and URL match `.testeiya/testeiya.json`; rerun with `DEBUG=testomatio:*` |
-
-The CLI calls `GET /api/test_data` and `POST /api/load` directly — not through Testeiya's proxy, so they never appear in `cli/log/testomatio.http`. Use `DEBUG=testomatio:*` instead.
-
-## Related skills
-
-- `sync-test-cases-with-tms` — the pull/edit/push workflow that wraps this CLI. Use it for the process, this for the tool surface.
-- `qa-write-test-cases` / `improve-test-cases` — produce and refine the `*.test.md` files; pass output via `push -f`.
-- `scan-automation-project` — detect the framework before a code import.
-- `qa-e2e-tests-reporting` / `testomatio-reporter` — report run RESULTS; check-tests imports definitions.
-- `qa-test-code-coverage` — map source files to imported test IDs.
-- `testomatio-mcp` — read/query the project over MCP instead of files.
-- `check-cucumber` — the sibling importer for Gherkin `.feature` files.

package/skills/testeiya/manual-run-assistant/SKILL.md

@@ -1,61 +0,0 @@
----
-name: manual-run-assistant
-description: Assist a human executing a manual test run in the browser. Create or resume the run, open the manual-run executor, prepare the environment (headed browser, login state, the page under test), hand each test to the user, and turn captured browser signals (console errors, failed requests, traces) into proposed testrun notes. Use to start, execute, pass, or assist a manual run; to prepare a browser for manual testing; or when a <manual-run-event> block reports a verdict or asks for signal analysis.
-license: MIT
-metadata:
-  author: Testomat.io
-  version: 1.0.0
----
-
-# Manual Run Assistant
-
-Semi-automated manual testing. The user executes tests and records verdicts in the manual-run executor widget; you prepare the environment, navigate, watch what the browser captured, and propose findings. You are the assistant, not the tester.
-
-## Use cases
-
-- Start or resume a manual run and open the executor for the user.
-- Prepare the environment: headed browser, saved login state, the page under test.
-- Walk the user through the run test by test, pre-navigating to each test's page.
-- Analyze a failed test's captured signals and propose a testrun note.
-- Attach evidence and finish the run with a findings summary.
-
-## The flow
-
-1. **Find or create the run.** Existing runs via MCP `runs_list`/`runs_get`. New: `runs_create` with `kind: "manual"` and the chosen `test_ids`/`suite_ids`/`plan_ids` — ask which tests belong in the run if unclear. The MCP create/update tools may be disabled — `enable_tools` them first. Then `render_item` (kind `run`) and drive the rendered card via the `widget_id` its ack names: `ui_widget` `start_manual_run` opens the executor, same turn.
-2. **Prepare the browser.** Check `<browser_state>`; no browser → `playwright-cli open --headed` (the shared session — never `attach --cdp`). Resolve the application-under-test URL by the browser rules — never guess; ask with the candidates you found. If login is needed, let the user sign in (bring the window to front), then offer `playwright-cli state-save` so later sessions skip it (`state-load` restores).
-3. **Per test.** `ui_widget` `select_test`, read its steps from `get()`, navigate the browser to the page step 1 starts on. Then hand off via `ask_question`: the user drives, or you execute while they verify. When the user drives: bring the browser to front, tell them to press **Start test** in the executor (starts the timer and signal capture), and **end your turn** — their verdict reaches you as a `<manual-run-event>` when you are idle.
-4. **On a `<manual-run-event>`** — see below.
-5. **Finish.** `ui_widget` `finish_run` when every test has a verdict (confirm first if some are pending). Then `runs_update` with a short `description`: outcome counts, validated findings, notable signals.
-
-## Handling `<manual-run-event>`
-
-The executor emits one when a saved verdict has evidence (failed, or browser errors were captured) or when the user clicks the signals badge mid-test. The block carries the testrun id, verdict, console errors, failed requests, and the trace path.
-
-- Deepen before judging: `playwright-cli console error`, `playwright-cli requests`, `playwright-cli request <n>` for a suspect request's headers/body. The trace file's `.network` sibling holds the full cross-page record.
-- Validate: does the error actually relate to the test's steps? A 404 on a tracking pixel does not fail a login test.
-- Validated → propose a short factual note via `ui_widget` `suggest_message`: what broke, the failing request (`[METHOD] url => status`), the console error, which step it surfaced on. The user applies or dismisses it.
-- Not validated → answer in one or two sentences; do not invent findings and do not suggest a note.
-- Worth keeping visually → `ui_widget` `attach_screenshot`.
-
-## Critical rules
-
-- **Verdicts belong to the user.** Never set or save a status for a test you did not execute and verify yourself.
-- **Propose, don't write.** Findings go through `suggest_message` — never `set_message` over the user's text, never `save_next` after a suggestion.
-- **`runs_create` without `test_ids`/`suite_ids`/`plan_ids` creates an EMPTY run** — zero testruns, nothing to execute. Always scope it, then confirm with `testruns_list` that the tests are there. Created an empty one by mistake? Delete it (`runs_delete`) — never leave orphan runs and create another.
-- **Runs are created via MCP, not `@testomatio/reporter`.** The reporter CLI is for automated/CI result reporting; its `--filter` needs tags registered in the project and fails otherwise.
-- **End the turn after a handoff.** Events can only start your turn while you are idle; a turn left open blocks them.
-- **Don't set run_time.** The executor's timer records it on save.
-- Never guess the target URL — the browser-testing rules apply to every navigation here.
-
-## How Testeiya wires it
-
-- The executor's actions are listed in the `<active_widget>` block; `get()` returns the run, its tests, and the live capture counts.
-- **Start test** starts a timer and `POST /api/playwright/capture/start`: a Playwright trace plus freshly cleared console/request lists in the shared `testeiya` browser session — your own `playwright-cli` calls read exactly what the user's actions produced.
-- Saving a verdict records the timed `run_time` (seconds), auto-attaches a browser screenshot, stops the capture, and emits the `<manual-run-event>` when there is something to analyze.
-- The signals badge in the executor shows live error/failed-request counts; clicking it sends you an analysis request with counts only — read the details yourself.
-
-## Related skills
-
-- `playwright-cli` — the browser command set.
-- `testomatio-mcp` — run/test queries beyond the widget.
-- `test-management/qa-thinking` — what else could be wrong beyond the failing step.

package/skills/testeiya/testomatio-docs/INDEX.md

@@ -1,175 +0,0 @@
-# Testomat.io documentation index
-
-140 pages vendored from https://github.com/testomatio/docs (`src/content/docs`) at commit `942895fc45fdf1cb5db1aa8322925ce5317d3028`.
-
-Every file listed below lives under `docs/` next to this index. Grep this file for a term,
-then read the matching page. Cite the public URL, never the local path.
-
-Format: `` `<file>` — **Title** — <public URL> — description ``
-
-## advanced
-
-- `advanced/ai-powered-features/ai-agents.md` — **AI-Agents** — https://docs.testomat.io/advanced/ai-features/ai-agents — Discover Testomat.io’s AI Agents — intelligent tools designed to automate test management tasks like identifying flaky tests, enhancing descriptions, and con...
-- `advanced/ai-powered-features/ai-powered-features.md` — **AI-Powered Features** — https://docs.testomat.io/advanced/ai-features/ai-powered-features — Learn how to use AI-powered generative features to simplify and enhance your test management workflows in Testomat.io. This guide covers how to work with AI-...
-- `advanced/ai-powered-features/ai-requirements.md` — **AI-Requirements** — https://docs.testomat.io/advanced/ai-features/ai-requirements — Discover Testomat.io's AI-powered features that analyze your requirements from Jira to enhance test coverage. Learn how this intelligent analysis helps impro...
-- `advanced/api-access/index.md` — **API Access** — https://docs.testomat.io/advanced/api-access — Learn how to use Testomat.io API tokens to securely connect and interact with your test management projects. This guide covers access token types, authentica...
-- `advanced/branches-folder/index.md` — **Branches** — https://docs.testomat.io/advanced/branches-folder — Learn how to manage test branching in Testomat.io for efficient collaboration. This guide covers creating branches for isolated test modifications, working w...
-- `advanced/bulk-edit-folder/bulk-edit-demos.mdx` — **Bulk Edit Demo - Creating and Restructuring Tests with YAML** — https://docs.testomat.io/advanced/bulk-edit-folder-demos — Watch Bulk Edit in action with real-world examples. This page demonstrates how to create tests, remove a root suite, and restructure test projects in Testoma...
-- `advanced/bulk-edit-folder/bulk-edit-on-suite-and-test-level.md` — **Bulk Edit on Suite and Test Levels** — https://docs.testomat.io/advanced/bulk-edit-folder-suites-and-tests — Learn how to use the Bulk Edit feature in Testomat.io to manage test suites more efficiently. This guide explains file and folder patterns, how to bulk edit...
-- `advanced/bulk-edit-folder/what-is-bulk-edit.md` — **Using Bulk Edit and YAML Format in Testomat.io** — https://docs.testomat.io/advanced/bulk-edit-folder — Discover how to manage large test projects in Testomat.io using the Bulk Edit feature. Learn how to restructure test suites, create and delete tests using YA...
-- `advanced/jira-plugin/branches.md` — **Work with Branches in Jira** — https://docs.testomat.io/advanced/jira-plugin/branches — Learn how to manage branches in the Testomat.io Jira plugin. This guide covers creating new branches, switching between branches and the main project, and wo...
-- `advanced/jira-plugin/index.mdx` — **Jira Plugin** — https://docs.testomat.io/advanced/jira-plugin — Learn how to integrate Testomat.io with Jira using the Jira plugin. This guide covers connecting projects, linking/unlinking tests, suites, and plans to Jira...
-- `advanced/jira-plugin/jira-issue.md` — **Creating Jira Issue** — https://docs.testomat.io/advanced/jira-plugin/jira-issue — Learn how to integrate Testomat.io with Jira using the Jira plugin. This guide covers connecting Testomat.io projects to Jira, linking/unlinking tests, suite...
-- `advanced/jira-plugin/runs-and-reports.md` — **Runs & Reports in Jira** — https://docs.testomat.io/advanced/jira-plugin/runs-and-reports — Learn how to run manual, automated, or mixed test executions in Jira using the Testomat.io plugin. This guide covers configuring advanced settings, executing...
-- `advanced/jira-plugin/work-in-jira.md` — **Work with Tests in Jira** — https://docs.testomat.io/advanced/jira-plugin/work-in-jira — Learn how to integrate Testomat.io with Jira using the Jira plugin. This guide covers connecting Testomat.io projects to Jira, linking/unlinking tests, suite...
-- `advanced/living-doc/index.md` — **Living Documentation** — https://docs.testomat.io/advanced/living-doc — Learn how to enable and embed Living Documentation in Testomat.io, a dynamic and real-time document generation tool for test projects. This guide covers embe...
-- `advanced/milestones/index.md` — **Milestones** — https://docs.testomat.io/advanced/milestones — Discover Testomat.io's Milestones feature to support structured test management across your development cycles. Learn how to create, activate, and assign mil...
-- `advanced/shortcuts/index.md` — **Keyboard Shortcuts** — https://docs.testomat.io/advanced/shortcuts — This guide covers keyboard shortcuts in Testomat.io to enhance efficiency when creating and editing tests. It includes shortcuts for opening windows, saving,...
-- `advanced/tags-labels/labels-and-custom-fields.md` — **Labels and Custom Fields** — https://docs.testomat.io/advanced/tags-labels/labels-and-custom-fields — Learn how to use labels and custom fields in Testomat.io to organize and categorize tests, suites, runs, plans, and steps. This guide covers creating and set...
-- `advanced/tags-labels/tags-or-labels.md` — **Tags or Labels** — https://docs.testomat.io/advanced/tags-labels/tags-or-labels — Discover how to use labels, custom fields and tags in Testomat.io to enhance your test management. This guide explains how to categorize and organize tests w...
-- `advanced/tags-labels/tags.md` — **Tags** — https://docs.testomat.io/advanced/tags-labels/tags — Learn how to create and assign tags in Testomat.io to organize test cases and suites. This guide explains the process of adding tags directly in the title, u...
-- `advanced/test-artifacts/index.md` — **Artifacts** — https://docs.testomat.io/advanced/test-artifacts/artifacts — Learn how Testomat.io handles test artifacts and attachments, such as screenshots, videos, and logs, to enhance test management and reporting. This guide exp...
-- `advanced/tql/index.md` — **Query Language** — https://docs.testomat.io/advanced/tql — 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, n...
-
-## getting-started
-
-- `getting-started/index.md` — **Start With Testomat.io** — https://docs.testomat.io/getting-started/start-from-scratch/ — This guide helps users start from scratch with Testomat.io by creating projects, writing test cases, running manual and automated tests, and analyzing result...
-
-## integrations
-
-- `integrations/continuous-integration/azure.md` — **Azure Pipelines** — https://docs.testomat.io/integrations/continuous-integration/azure — Integrate Azure Pipelines with Testomat.io to automate test execution and reporting. This guide explains setting up CI connections, creating input variables,...
-- `integrations/continuous-integration/bamboo.md` — **Atlassian Bamboo** — https://docs.testomat.io/integrations/continuous-integration/bamboo — This guide explains integrating Atlassian Bamboo with Testomat.io for continuous integration. It includes configuring Bamboo plans, setting environment varia...
-- `integrations/continuous-integration/bitbucket.md` — **BitBucket Pipelines** — https://docs.testomat.io/integrations/continuous-integration/bitbucket — Integrate Bitbucket Pipelines with Testomat.io to streamline test execution and reporting. This guide explains setting up API tokens, configuring pipeline pa...
-- `integrations/continuous-integration/circle.md` — **Circle CI** — https://docs.testomat.io/integrations/continuous-integration/circle — Integrate CircleCI with Testomat.io to automate test execution and reporting. This guide explains configuring the config.yml workflow, setting parameters, an...
-- `integrations/continuous-integration/github.md` — **GitHub Actions** — https://docs.testomat.io/integrations/continuous-integration/github — This guide explains how to integrate GitHub Actions with Testomat.io for continuous integration. It includes creating workflows, setting up environment varia...
-- `integrations/continuous-integration/gitlab.md` — **GitLab CI** — https://docs.testomat.io/integrations/continuous-integration/gitlab — Learn how to integrate GitLab CI with Testomat.io to automate test execution and reporting. The guide covers configuring .gitlab-ci.yml, passing environment...
-- `integrations/continuous-integration/index.mdx` — **Continuous Integration** — https://docs.testomat.io/integrations/continuous-integration — Explore how to integrate continuous testing into your CI/CD pipeline using Testomat.io. This guide explains the setup process for Continuous Integration (CI)...
-- `integrations/continuous-integration/jenkins.md` — **Jenkins** — https://docs.testomat.io/integrations/continuous-integration/jenkins — Learn how to integrate Jenkins with Testomat.io for continuous integration. This guide covers creating Jenkins jobs, configuring parameters, triggering build...
-- `integrations/continuous-integration/teamcity.md` — **TeamCity** — https://docs.testomat.io/integrations/continuous-integration/teamcity — Integrate TeamCity with Testomat.io for automated test execution and reporting. The guide details creating projects and build configurations in TeamCity, set...
-- `integrations/issues-management/azure.md` — **Azure DevOps Configuration** — https://docs.testomat.io/integrations/issues-management/azure — Integrate Azure DevOps with Testomat.io for efficient issue tracking and test management. This guide explains setting up a profile using an Azure DevOps pers...
-- `integrations/issues-management/clickup.md` — **ClickUp Configuration** — https://docs.testomat.io/integrations/issues-management/clickup — Learn how to integrate ClickUp with Testomat.io for efficient issue management. This guide provides step-by-step instructions to retrieve your ClickUp API to...
-- `integrations/issues-management/confluence.md` — **Confluence** — https://docs.testomat.io/integrations/issues-management/confluence — Learn how to connect your Confluence space with Testomat.io for issue management. This guide walks you through obtaining your Project Access Token on Atlassi...
-- `integrations/issues-management/github.md` — **GitHub Issues Configuration** — https://docs.testomat.io/integrations/issues-management/github — Configure GitHub Issues integration in Testomat.io to create and manage issues directly from your test management system. This setup involves providing a Git...
-- `integrations/issues-management/gitlab.md` — **GitLab Configuration** — https://docs.testomat.io/integrations/issues-management/gitlab — Learn how to integrate GitLab with Testomat.io for issue management. This guide walks you through obtaining your Group Name, Project ID, and Project Access T...
-- `integrations/issues-management/index.md` — **Issues Management Systems** — https://docs.testomat.io/integrations/issues-management — Learn how to integrate issues management systems like Jira, GitHub, Azure DevOps with Testomat.io. This guide covers configuring connections to these systems...
-- `integrations/issues-management/jira.md` — **Jira** — https://docs.testomat.io/integrations/issues-management/jira — The Jira integration for Testomat.io allows two-way synchronization of test cases and issues. By connecting a Testomat.io project to a Jira project, users ca...
-- `integrations/issues-management/linear.md` — **Linear Configuration** — https://docs.testomat.io/integrations/issues-management/linear — Integrate Linear with Testomat.io to streamline issue tracking directly from your test management system. This setup involves configuring a profile with your...
-- `integrations/issues-management/shortcut.md` — **Shortcut Configuration** — https://docs.testomat.io/integrations/issues-management/shortcut — Learn how to integrate Shortcut with Testomat.io for effective issue tracking. This guide details how to retrieve your API Access Token and Workflow Name and...
-- `integrations/issues-management/youtrack.md` — **YouTrack Configuration** — https://docs.testomat.io/integrations/issues-management/youtrack — Learn how to integrate YouTrack with Testomat.io for streamlined issue management. This guide explains how to retrieve your YouTrack Workspace Name, Personal...
-- `integrations/report-notifications/azure-devops.md` — **Azure DevOps Notifications** — https://docs.testomat.io/integrations/report-notifications/azure-devops — Configure Azure DevOps notifications in Testomat.io to automate issue creation for failed test runs. This guide explains linking Azure DevOps projects, and s...
-- `integrations/report-notifications/email.md` — **Email Notifications** — https://docs.testomat.io/integrations/report-notifications/email — Learn how to configure email notifications in Testomat.io to receive updates on test run results. This guide covers setting notification rules, customizing f...
-- `integrations/report-notifications/jira.md` — **Jira Notifications** — https://docs.testomat.io/integrations/report-notifications/jira — Configure Jira notifications in Testomat.io to automate issue creation for failed test runs. This guide explains linking Jira projects, selecting issue types...
-- `integrations/report-notifications/ms-teams.md` — **Microsoft Teams Notifications** — https://docs.testomat.io/integrations/report-notifications/ms-teams — Configure Microsoft Teams notifications in Testomat.io to receive test updates. This guide provides detailed steps for setting up incoming webhooks in Teams,...
-- `integrations/report-notifications/rules.md` — **Notification Rules** — https://docs.testomat.io/integrations/report-notifications/rules — Learn how to configure and manage notifications in Testomat.io for various channels, including Email, Slack, MS Teams, and Jira. This guide covers setting up...
-- `integrations/report-notifications/slack.md` — **Slack Notifications** — https://docs.testomat.io/integrations/report-notifications/slack — Learn to configure Slack notifications in Testomat.io to receive test run updates directly in a Slack channel. The guide explains creating a Slack app, enabl...
-- `integrations/report-notifications/telegram.md` — **Telegram Notifications** — https://docs.testomat.io/integrations/report-notifications/telegram — Configure Telegram notifications in Testomat.io to receive test updates. This guide provides detailed steps for creating a Telegram bot, generating a Bot Tok...
-- `integrations/scim-provisioning/index.mdx` — **SCIM provisioning overview** — https://docs.testomat.io/integrations/scim-provisioning — Automate user provisioning and de-provisioning in Testomat.io using SCIM (System for Cross-domain Identity Management) with identity providers like Okta, Mic...
-- `integrations/scim-provisioning/okta.md` — **Configure SCIM with Okta** — https://docs.testomat.io/integrations/scim-provisioning/okta — Learn how to configure SCIM (System for Cross-domain Identity Management) provisioning with Okta for Testomat.io. This guide explains setting up SCIM provisi...
-- `integrations/single-sign-on/azure.md` — **Microsoft Entra ID (formerly Azure AD)** — https://docs.testomat.io/integrations/single-sign-on/azure — Learn how to set up Single Sign-On (SSO) for Testomat.io with Microsoft Entra ID (formerly Azure AD) using SAML authentication. This guide explains configuri...
-- `integrations/single-sign-on/google.md` — **Google Workspace** — https://docs.testomat.io/integrations/single-sign-on/google — Learn how to configure Google Workspace Single Sign-On (SSO) for Testomat.io using SAML authentication. The guide explains the steps to create a custom SAML...
-- `integrations/single-sign-on/index.mdx` — **Single Sign-On** — https://docs.testomat.io/integrations/single-sign-on — Set up Single Sign-On (SSO) for Testomat.io using SAML with various identity providers like Okta, Google Workspace, and Azure AD. This guide walks through co...
-- `integrations/single-sign-on/okta.md` — **Okta** — https://docs.testomat.io/integrations/single-sign-on/okta — Learn how to configure Okta Single Sign-On (SSO) with Testomat.io using SAML authentication. This guide explains setting up the integration, assigning users,...
-- `integrations/single-sign-on/saml.md` — **Custom SAML** — https://docs.testomat.io/integrations/single-sign-on/saml — This guide explains integrating custom SAML providers with Testomat.io for Single Sign-On (SSO). It includes steps to configure the SAML application, set use...
-
-## legal
-
-- `legal/compliance/gdpr.md` — **GDPR Commitment** — https://docs.testomat.io/legal/compliance/gdpr — Testomat.io is fully committed to GDPR compliance, ensuring the protection of personal data in line with European regulations. It collects only essential dat...
-- `legal/compliance/index.mdx` — **Testomat.io Compliance Overview** — https://docs.testomat.io/legal/compliance — Testomat.io’s Compliance Overview emphasizes adherence to legal standards, ensuring trust and transparency for users. Key practices include 24/7 system monit...
-- `legal/compliance/privacy.md` — **Privacy Policy** — https://docs.testomat.io/legal/compliance/privacy — Testomat.io's Privacy Policy explains how user data is collected, used, and protected. It covers the collection of personal data (e.g., names, emails), its u...
-- `legal/compliance/terms.md` — **Terms of Service** — https://docs.testomat.io/legal/compliance/terms — Testomat.io’s Terms of Service govern the use of its platform, covering topics such as account creation, subscription payments, refunds, prohibited uses, and...
-- `legal/security/index.mdx` — **Testomat.io Security Overview** — https://docs.testomat.io/legal/security — Testomat.io’s Security Overview outlines robust measures to ensure data integrity, confidentiality, and availability. It features encryption, access controls...
-- `legal/security/jira.md` — **JIRA Plugin Permissions and Security** — https://docs.testomat.io/legal/security/jira — The Testomat.io JIRA plugin enhances integration with JIRA projects by linking test cases to issues. It offers read access to project issues and writes prope...
-- `legal/security/subprocessors.md` — **Subprocessors** — https://docs.testomat.io/legal/security/subprocessors — Testomat.io uses subprocessors including DigitalOcean, Hetzner, and Google Cloud for core infrastructure and data storage, Cloudflare for traffic management,...
-
-## management
-
-- `management/company/administration.md` — **Administration** — https://docs.testomat.io/management/company/administration — This page outlines administrative controls available to company owners in Testomat.io, including managing all projects within an organization. Owners can ove...
-- `management/company/audit-log.md` — **Audit Log** — https://docs.testomat.io/management/company/audit-log — Explore an Audit Log feature that is available inside the Testomat.io. It is available on a Company level for Owners and Manageres. It monitors creation deta...
-- `management/company/plan-features-comparison.md` — **Plan Features Comparison** — https://docs.testomat.io/management/company/plan-features-comparison — Compare features across Free, Professional, and Enterprise plans in Testomat.io. This guide helps you evaluate test management, automation, integrations, rep...
-- `management/company/subscriptions.md` — **Subscriptions** — https://docs.testomat.io/management/company/subscriptions — Explore the subscription options in Testomat.io, including Free, Professional, and Enterprise plans. This guide outlines how to manage subscriptions, upgrade...
-- `management/company/trials.md` — **Trials** — https://docs.testomat.io/management/company/trials — Testomat.io offers a Free 30-Day Trial and an additional 14-Day Trial for users to explore all features, including test automation, Jira integration, and not...
-- `management/company/users-and-permissions/accountant.md` — **Accountant User Role in Testomat.io** — https://docs.testomat.io/management/company/users-and-permissions/accountant — Learn how the Accountant user role works in Testomat.io, including permissions, restrictions, and how to assign this role for free to manage billing and fina...
-- `management/company/users-and-permissions/index.mdx` — **Users Roles & Access Overview** — https://docs.testomat.io/management/company/users-and-permissions — Manage users and permissions in Testomat.io with ease. Learn how to invite users, assign roles (Owner, Manager, QA, Accountant, Read-Only), add users to proj...
-- `management/company/users-and-permissions/read-only-user.md` — **Read-Only User Role in Testomat.io** — https://docs.testomat.io/management/company/users-and-permissions/read-only-user — Learn how to add or manage Read-Only users in Testomat.io to provide stakeholders with view-only access to test cases, reports, and analytics without editing...
-- `management/company/users-and-permissions/teams.md` — **Managing Teams in Testomat.io** — https://docs.testomat.io/management/company/users-and-permissions/teams — Learn how to create and manage teams in Testomat.io to simplify user access across multiple projects by grouping users and assigning team-level permissions.
-- `management/project/settings.md` — **Project setup and management** — https://docs.testomat.io/management/project/settings — Discover how to manage project settings in Testomat.io, including configuring the project timezone for teams across different regions. This guide outlines st...
-- `management/project/templates.md` — **Templates** — https://docs.testomat.io/management/project/templates — Learn how to create, edit, and apply templates in Testomat.io to standardize your testing and defect reporting workflows. This guide covers template manageme...
-
-## project
-
-- `project/analytics/index.md` — **Analytics** — https://docs.testomat.io/project/analytics — Explore Testomat.io's Analytics feature to monitor testing performance. This guide explains how to track automated and manual tests, customize analytics view...
-- `project/import-export/export-tests/classical-tests-markdown-format.md` — **Classical Tests Markdown Format** — https://docs.testomat.io/project/import-export/export-tests/classical-tests-markdown-format — Complete reference for the Testomat.io classical tests Markdown format. Learn the structure, metadata fields, and formatting rules for test suites and test c...
-- `project/import-export/export-tests/download-manual-tests-as-files.md` — **Download Manual Tests as Files** — https://docs.testomat.io/project/import-export/export-tests/download-manual-tests-as-files — Learn how to manage manual tests using Git version control by exporting them from Testomat.io as Markdown files. This guide details how to export tests, trac...
-- `project/import-export/export-tests/export-to-obsidian.md` — **Export Tests to Obsidian** — https://docs.testomat.io/project/import-export/export-tests/export-to-obsidian — Export manual tests from Testomat.io as Markdown files and open them in Obsidian as a vault. Browse, search, edit test cases in Obsidian and push changes bac...
-- `project/import-export/export-tests/export-to-spreadsheet.md` — **Export to Spreadsheet** — https://docs.testomat.io/project/import-export/export-tests/export-to-spreadsheet — Learn how to export test cases and suites from Testomat.io in spreadsheet (Excel) format. This guide covers exporting all tests, entire suites, or filtered r...
-- `project/import-export/import/auto-import.md` — **Auto-Import** — https://docs.testomat.io/project/import-export/auto-import — Learn how to automatically import and update your test cases in Testomat.io using GitHub Actions. This guide explains how to set up a workflow to sync automa...
-- `project/import-export/import/import-tests-from-Allure-TestOps.md` — **Import Tests From Allure TestOps** — https://docs.testomat.io/project/import-export/import-tests-from-allure-testops — Learn how to import tests from Allure TestOps using a customizable migration script for more advanced, tailored imports.
-- `project/import-export/import/import-tests-from-csv-xlsx.md` — **Import from CSV/XLSX** — https://docs.testomat.io/project/import-export/import-tests-from-csv-xlsx — Learn how to import tests from CSV or XLSX files into Testomat.io. This guide covers the process of importing test cases from systems like TestRail, Zephyr,...
-- `project/import-export/import/import-tests-from-cucumber.md` — **Import Tests From Cucumber** — https://docs.testomat.io/project/import-export/import-tests-from-cucumber — Learn how to import tests from Cucumber into Testomat.io for better visibility and management. This guide covers steps to create a new project, select the ap...
-- `project/import-export/import/import-tests-from-Qase.md` — **Import Tests From Qase** — https://docs.testomat.io/project/import-export/import-tests-from-qase — Learn how to import tests from Qase using the CSV import feature in Testomat.io. This guide walks you through formatting and uploading your test cases, makin...
-- `project/import-export/import/import-tests-from-qmetry.md` — **Import Tests From QMetry** — https://docs.testomat.io/project/import-export/import-tests-from-qmetry — Learn how to import tests from QMetry using a customizable migration script for more advanced, tailored imports.
-- `project/import-export/import/import-tests-from-QTest.md` — **Import Tests From QTest** — https://docs.testomat.io/project/import-export/import-tests-from-qtest — Learn how to import tests from qTest using the CSV import feature in Testomat.io. This guide walks you through formatting and uploading your test cases, maki...
-- `project/import-export/import/import-tests-from-source-code.md` — **Import Tests From Source Code** — https://docs.testomat.io/project/import-export/import-tests-from-source-code — Learn how to import existing end-to-end or unit tests directly from your source code into Testomat.io. This guide covers creating a project and configuring t...
-- `project/import-export/import/import-tests-from-testcaselabs.md` — **Import Tests From TestCaseLabs** — https://docs.testomat.io/project/import-export/import-tests-from-testcaselabs — Learn how to import tests from TestCaseLabs using a customizable migration script for more advanced, tailored imports.
-- `project/import-export/import/import-tests-from-testmo.md` — **Import Tests From Testmo** — https://docs.testomat.io/project/import-export/import-tests-from-testmo — Learn how to import tests from Testmo using two flexible methods - the built-in CSV import and a customizable migration script. This guide walks you through...
-- `project/import-export/import/import-tests-from-testrail.md` — **Import Tests From TestRail** — https://docs.testomat.io/project/import-export/import-tests-from-testrail — Learn how to export tests from TestRail using three different methods CSV export, the built-in UI tool, and the migration script. This guide walks you throug...
-- `project/import-export/import/import-tests-from-xray.md` — **Import Tests From XRay** — https://docs.testomat.io/project/import-export/import-tests-from-xray — Learn how to import tests from XRay into Testomat.io using the migration script that utilizes the XRay API.
-- `project/import-export/import/import-tests-from-Zephyr.md` — **Import Tests From Zephyr** — https://docs.testomat.io/project/import-export/import-tests-from-zephyr — Learn how to import tests from Zephyr using the CSV import feature in Testomat.io. This guide walks you through formatting and uploading your test cases, mak...
-- `project/plans/index.md` — **Test Plans Overview** — https://docs.testomat.io/project/plans — Explore how to create and manage test plans in Testomat.io. This guide covers manual, automated, and mixed test plans, detailing how to organize test cases,...
-- `project/pulse/index.md` — **Pulse** — https://docs.testomat.io/project/pulse — Pulse in Testomat.io tracks all changes to tests, test suites, test plans, and test runs, providing transparency and control over project modifications. It t...
-- `project/runs/archive-runs-and-groups.md` — **Archive Runs & RunGroups** — https://docs.testomat.io/project/runs/archive-runs-and-groups — Testomat.io's archiving feature helps users maintain a clean and organized Runs Dashboard by moving irrelevant test runs and groups to dedicated archive sect...
-- `project/runs/custom-statuses.md` — **Custom Statuses** — https://docs.testomat.io/project/runs/custom-statuses — Learn how to use custom test result statuses in Testomat.io. This guide explains how to configure additional result messages, apply them during manual test r...
-- `project/runs/environments.md` — **Environments** — https://docs.testomat.io/project/runs/environments — Learn how to configure, manage, and view test results across multiple environments in Testomat.io. This guide covers environment setup in project settings, t...
-- `project/runs/managing-runs.md` — **Managing Runs** — https://docs.testomat.io/project/runs/managing-runs — Learn how to manage test runs effectively in Testomat.io. This guide covers generating detailed run reports, organizing runs into groups, applying merge stra...
-- `project/runs/merge-strategies.md` — **Merge Strategies** — https://docs.testomat.io/project/runs/merge-strategies — Learn how 'Merge Strategies' in Testomat.io can help you to consolidate test results from multiple runs within a RunGroup, providing a unified view of your t...
-- `project/runs/reports.md` — **Run Reports** — https://docs.testomat.io/project/runs/reports — Learn how Testomat.io generates comprehensive Run Reports for both manual and automated tests, offering basic and extended views. This guide covers features...
-- `project/runs/rungroups.md` — **RunGroups** — https://docs.testomat.io/project/runs/rungroups — Testomat.io's 'RunGroups' feature allows users to organize multiple test runs based on criteria like sprint or release, providing a consolidated view of test...
-- `project/runs/running-automated-tests.md` — **Running Automated Tests** — https://docs.testomat.io/project/runs/running-automated-tests — Learn how to run automated tests using Testomat.io. This guide walks through the process of importing tests, generating run reports, and configuring automate...
-- `project/runs/running-manual-and-automated-tests.md` — **Running Manual and Automated Tests** — https://docs.testomat.io/project/runs/running-manual-and-automated-tests — Learn how to execute manual and automated tests together using Mixed Run. This guide explains execution types (CI or local), launch flows from different page...
-- `project/runs/running-tests-manually.md` — **Running Tests Manually** — https://docs.testomat.io/project/runs/running-tests-manually — Learn how to execute manual tests using Testomat.io. This guide covers creating test plans, running multi-environment tests, and executing manual tests as ch...
-- `project/runs/temporary-tests-notes.md` — **Temporary Tests - Notes** — https://docs.testomat.io/project/runs/temporary-tests-notes — Learn how to use Notes in Testomat.io to create, manage, and convert temporary test cases directly during manual test runs. This guide covers creating Notes...
-- `project/steps-snippets/snippets.md` — **Snippets** — https://docs.testomat.io/project/steps-snippets/snippets — A snippet - is a piece of text or collection of steps that can be used as autocompletion during creating tests. This can be used for any part of a test case.
-- `project/steps-snippets/steps.md` — **Steps Database** — https://docs.testomat.io/project/steps-snippets/steps — Learn how to utilize the Steps Database in Testomat.io to store, reuse, and auto-complete test steps across projects. This guide covers creating, editing, re...
-- `project/tests/bdd-test-case-editor.md` — **BDD Test Case Editor** — https://docs.testomat.io/project/bdd_editor — Learn how to write and manage BDD test scenarios using Testomat.io. This guide explores creating Gherkin-based tests, editing feature files, and using BDD wo...
-- `project/tests/classical-test-case-editor.md` — **Classical Test Case Editor** — https://docs.testomat.io/project/classical_editor — Learn how to create effective test designs with Testomat.io. This guide covers building test scenarios, using various test design techniques, and integrating...
-- `project/tests/classical-vs-bdd.md` — **Classical vs BDD** — https://docs.testomat.io/project/classical_vs_bdd — Learn the fundamental differences between Classical and BDD projects in Testomat.io and why they must remain separate. This guide covers Markdown vs. Gherkin...
-- `project/tests/copy-and-move-your-tests.md` — **Copy and Move your Tests** — https://docs.testomat.io/project/copy_move_tests — Learn how to create effective test designs with Testomat.io. This guide covers building test scenarios, using various test design techniques, and integrating...
-- `project/tests/other-features-for-test-case-design.md` — **Other Features for Test case Design** — https://docs.testomat.io/project/test_design_features — Learn how to use Testomat.io's test design features to manage test cases, apply design techniques, and organize your test structure effectively for automatio...
-- `project/tests/test-case-creation-and-editing.md` — **Test Case Creation and Editing** — https://docs.testomat.io/project/tests — Learn how to create and manage test cases effectively in Testomat.io. This guide covers building test scenarios, applying various test design techniques, and...
-
-## support
-
-- `support/index.md` — **Contact Us** — https://docs.testomat.io/support — Get in touch with Testomat.io for questions on product features, user flows, subscriptions, and pricing. Reach their team via Slack, Crisp chat, or email for...
-
-## test-reporting
-
-- `test-reporting/artifacts.md` — **Artifacts** — https://docs.testomat.io/test-reporting/artifacts — Understand how to manage and upload test artifacts in Testomat.io using external S3-compatible storage. This guide covers configuring public and private acce...
-- `test-reporting/cli.md` — **CLI** — https://docs.testomat.io/test-reporting/cli — Learn how to use the Testomat.io Reporter CLI, a powerful command-line tool for managing and automating test runs. This guide covers installation and general...
-- `test-reporting/configuration.md` — **Configuration** — https://docs.testomat.io/test-reporting/configuration — This guide outlines how to configure Testomat.io Reporter using environment variables. It explains how to pass variables inline, via .env files, or CI secret...
-- `test-reporting/frameworks.md` — **NodeJS Test Frameworks** — https://docs.testomat.io/test-reporting/frameworks — The Testomat.io framework integration guide explains how to implement different testing frameworks and reporting tools. It details configuration options for...
-- `test-reporting/functions.md` — **Functions** — https://docs.testomat.io/test-reporting/functions — Explore Testomat.io's flexible reporting functions to enhance your test reports. Learn to use functions like artifact, log, and step for adding files, loggin...
-- `test-reporting/index.mdx` — **Testomat.io Test Reporting** — https://docs.testomat.io/test-reporting/overview — The Testomat.io Reporter is a Node.js package designed to send test results directly to Testomat.io. It supports real-time reports, artifact uploads, and log...
-- `test-reporting/junit.md` — **JUnit Reporter** — https://docs.testomat.io/test-reporting/junit — Learn how to use the JUnit reporter with Testomat.io to upload XML test reports from various frameworks like JUnit, Pytest, NUnit, and more. Testomat.io auto...
-- `test-reporting/logger.md` — **Logger** — https://docs.testomat.io/test-reporting/logger — Learn how to use Testomat.io’s Logger to intercept and attach log messages from various logging frameworks (e.g., Winston, Pino) to your test reports. The Lo...
-- `test-reporting/php.md` — **PHP Test Frameworks** — https://docs.testomat.io/test-reporting/php — Learn how to integrate PHP test frameworks like Codeception and PHPUnit with Testomat.io. The guide covers installation, setting API keys, and configuring te...
-- `test-reporting/pipes/bitbucket.md` — **Bitbucket** — https://docs.testomat.io/test-reporting/pipes/bitbucket — Learn how to integrate Testomat.io with Bitbucket Pipes to streamline test reporting in pull requests. Automatically add test run summaries, including status...
-- `test-reporting/pipes/csv.md` — **CSV** — https://docs.testomat.io/test-reporting/pipes/csv — The CSV Pipe in Testomat.io allows you to export test results as a CSV file by setting the TESTOMATIO_CSV_FILENAME environment variable. This functionality i...
-- `test-reporting/pipes/debug.md` — **Debug** — https://docs.testomat.io/test-reporting/pipes/debug — The Debug Pipe is used to store data for debugging purposes in a temporary json file.
-- `test-reporting/pipes/github.md` — **Github** — https://docs.testomat.io/test-reporting/pipes/github — The GitHub Pipe feature in Testomat.io enables automated comments on pull requests, summarizing test results with key metrics like passed/failed/skipped test...
-- `test-reporting/pipes/gitlab.md` — **GitLab** — https://docs.testomat.io/test-reporting/pipes/gitlab — The GitLab Pipe in Testomat.io enables automatic test result reporting directly into GitLab merge requests. It provides detailed test metrics, including pass...
-- `test-reporting/pipes/html.md` — **HTML** — https://docs.testomat.io/test-reporting/pipes/html — Discover how to use Testomat.io's HTML Pipe to generate detailed HTML reports from your test runs. Learn how to configure environment variables to save repor...
-- `test-reporting/pipes/index.mdx` — **Pipes** — https://docs.testomat.io/test-reporting/pipes/overview — Testomat.io's Pipes feature allows you to forward test data from your test framework to other services like GitHub, GitLab, or CSV reports. Pipes are configu...
-- `test-reporting/pipes/testomatio.md` — **Advanced Options** — https://docs.testomat.io/test-reporting/pipes/testomatio — Learn how to use the Testomat.io Pipe for advanced reporting configurations in test automation. The guide covers setting environment variables, adding report...
-- `test-reporting/python.md` — **Python Test Frameworks** — https://docs.testomat.io/test-reporting/python — Learn how to integrate the Testomat.io reporter with Python test frameworks like Pytest. The documentation covers installation, synchronizing tests, configur...
-- `test-reporting/workflows.md` — **Workflows** — https://docs.testomat.io/test-reporting/workflows — This guide covers various Continuous Integration (CI) workflows using Testomat.io Reporter, including configurations for GitHub Actions, Azure Pipelines, and...
-
-## tutorials
-
-- `tutorials/Interacting-via-API.md` — **Interacting via API** — https://docs.testomat.io/tutorials/interacting-via-api — Learn how to interact with the Testomat.io API. This guide walks you through choosing an access token, authenticating to receive a JWT, listing suites and te...
-- `tutorials/java.md` — **Java** — https://docs.testomat.io/tutorials/java — Learn how to integrate Java test frameworks with Testomat.io for efficient test management and reporting. This guide covers importing JUnit, TestNG tests, ma...
-- `tutorials/Manual-Testing-Classic.md` — **Manual Testing - Classic** — https://docs.testomat.io/tutorials/manual-testing-classic — Learn how to run manual tests in a Classical project in Testomat.io. This guide walks you through creating a project, adding a suite, writing test cases in t...
-- `tutorials/playwright.md` — **Playwright** — https://docs.testomat.io/tutorials/playwright — Learn how to integrate Playwright with Testomat.io for efficient test management and reporting. The guide covers importing Playwright tests, managing paramet...
-- `tutorials/Set-Up-Read-Only-Access.md` — **Set Up Read-Only Access** — https://docs.testomat.io/tutorials/set-up-read-only-access — Learn how to give stakeholders a view-only look at your testing in Testomat.io. This guide walks you through inviting an external user with the Read-Only rol...
-- `tutorials/Using-AI-in-Testing.md` — **Using AI in Testing** — https://docs.testomat.io/tutorials/using-ai-in-testing — Learn how to use AI across a full testing cycle in Testomat.io. This guide walks you through enabling AI, connecting a custom AI provider, adding a requireme...
-- `tutorials/webdriver.md` — **WebdriverIO** — https://docs.testomat.io/tutorials/webdriverio — Learn how to integrate WebdriverIO with Testomat.io for efficient test management and reporting. This guide covers importing WebdriverIO tests, managing para...
-- `tutorials/Working-with-Jira.md` — **Working with Jira** — https://docs.testomat.io/tutorials/working-with-jira — Learn how to work with Jira in Testomat.io. This guide walks you through connecting your project to Jira, linking tests, suites, and plans to Jira issues, cr...