testeiya 0.6.0 → 0.8.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "testeiya",
-  "version": "0.6.0",
+  "version": "0.8.0",
   "description": "AI testing agent — QA-focused coding agent for manual and automated tests",
   "type": "module",
   "license": "MIT",
@@ -15,6 +15,8 @@
   "files": [
     "dist",
     "prompt",
+    "pipelines",
+    "PIPELINES.md",
     "skills",
     "mcp-tools.json",
     "README.md",
@@ -47,17 +49,17 @@
     "@earendil-works/pi-ai": "^0.84.3",
     "@earendil-works/pi-coding-agent": "^0.84.3",
     "@earendil-works/pi-tui": "^0.84.3",
-    "@testomatio/mcp": "^2.1.1",
+    "@testomatio/mcp": "^3.1.0",
     "chalk": "^5.6.2",
     "dedent": "^1.7.2",
     "pi-mcp-adapter": "^2.21.1",
-    "typebox": "1.3.7"
+    "typebox": "1.3.7",
+    "yaml": "^2.9.0"
   },
   "devDependencies": {
     "@types/node": "^22.19.19",
     "esbuild": "^0.28.1",
     "tsx": "^4.23.12",
-    "typescript": "^5.9.3",
-    "yaml": "^2.9.0"
+    "typescript": "^5.9.3"
   }
 }

package/pipelines/api-testing.yml

@@ -0,0 +1,39 @@
+name: api-testing
+description: Find the API endpoints a pull request changed, test each with Explorbot, explain what broke.
+
+gates:
+  api:
+    env: [EXPLORBOT_URL, EXPLORBOT_API_SPEC]
+    message: No API to test. Set EXPLORBOT_URL to the API base and EXPLORBOT_API_SPEC to its OpenAPI spec.
+  explorbot-ai:
+    env: [EXPLORBOT_AI_PROVIDER]
+    message: Explorbot has no AI provider. Set EXPLORBOT_AI_PROVIDER and its key.
+
+env:
+  EXPLORBOT_OUTPUT: ${PIPELINE_DIR}/explorbot
+  EXPLORBOT_NO_BANNER: "1"
+
+stages:
+  - id: review
+    session: qa
+    task: |
+      Review this pull request as a QA engineer. /qa-review-pr
+      List every API endpoint it adds or changes in endpoints.txt, one path per line, like /users/{id}.
+      Leave the file empty when no endpoint changed.
+    outputs: [endpoints.txt]
+
+  - id: explore
+    when: [api, explorbot-ai]
+    each_line: endpoints.txt
+    run: npx -y explorbot api explore "$ITEM" --style psycho
+    outputs: [explorbot/]
+    timeout: 10m
+
+  - id: results
+    session: qa
+    when: [api, explorbot-ai]
+    task: |
+      Explorbot results are under explorbot/: plans, request logs, and a session report. Read them.
+      Say which failures are real defects in this change: a broken contract, missing validation, a wrong status.
+      Fail the run if any is a real defect.
+    inputs: [endpoints.txt, explorbot/]

package/pipelines/issue-test-cases.yml

@@ -0,0 +1,41 @@
+name: issue-test-cases
+description: Turn an issue or epic into test cases, and sync them to Testomat.io.
+
+gates:
+  issue:
+    env: [ISSUE_URL]
+    message: No issue. Set ISSUE_URL to the issue or epic to cover.
+  testomatio:
+    env: [TESTOMATIO, TESTOMATIO_PROJECT_ID]
+    message: No Testomat.io project. Set TESTOMATIO and TESTOMATIO_PROJECT_ID.
+
+when: [issue]
+
+stages:
+  - id: requirements
+    session: analyst
+    task: |
+      Read the issue at ${ISSUE_URL}: its body, its comments, and every linked issue.
+      An epic has sub-issues. Read each one. On GitHub, `gh issue view <url> --comments`
+      reads an issue and `gh api repos/<owner>/<repo>/issues/<number>/sub_issues` lists sub-issues.
+      Review the requirements as a QA engineer. /qa-requirement-reviewer
+      Write the acceptance criteria to criteria.md, one section per sub-issue or feature area.
+      End it with the open questions and gaps you found.
+      The code here may not implement the issue yet. Read it only to use the real names of screens and terms.
+    outputs: [criteria.md]
+
+  - id: test-cases
+    session: writer
+    task: |
+      Write test cases from criteria.md. /qa-write-test-cases
+      Put them in test-cases/, one markdown file per suite, one suite per sub-issue or feature area.
+      Cover every criterion. A case that depends on an open question says so in its description.
+    inputs: [criteria.md]
+    outputs: [test-cases/]
+
+  - id: sync
+    when: [testomatio]
+    each_file: test-cases/*.md
+    task: |
+      Sync the test cases in ${ITEM} to Testomat.io. /sync-test-cases-with-tms
+      Skip a case that already exists there.

package/pipelines/pr-review.yml

@@ -0,0 +1,43 @@
+name: pr-review
+description: Review a pull request, propose test cases for it, and sync them to Testomat.io.
+
+gates:
+  code-changed:
+    changes:
+      min_files: 3
+      ignore: ["**/*.md", "**/*.lock", "docs/**"]
+    message: Fewer than 3 code files changed.
+  testomatio:
+    env: [TESTOMATIO, TESTOMATIO_PROJECT_ID]
+    message: No Testomat.io project. Set TESTOMATIO and TESTOMATIO_PROJECT_ID.
+
+when: [code-changed]
+
+stages:
+  - id: requirements
+    session: reviewer
+    task: |
+      Work out what this pull request is meant to do. /qa-pr-requirements-analyzer
+      Write the acceptance criteria to criteria.md.
+    outputs: [criteria.md]
+
+  - id: review
+    session: reviewer
+    task: |
+      Review this pull request as a QA engineer against criteria.md. /qa-review-pr
+    inputs: [criteria.md]
+
+  - id: test-cases
+    session: writer
+    task: |
+      Write test cases for this pull request from criteria.md and review.md. /qa-write-test-cases
+      Put them in test-cases/, one markdown file per suite.
+    inputs: [criteria.md, review.md]
+    outputs: [test-cases/]
+
+  - id: sync
+    when: [testomatio]
+    each_file: test-cases/*.md
+    task: |
+      Sync the test cases in ${ITEM} to Testomat.io. /sync-test-cases-with-tms
+      Skip a case that already exists there.

package/pipelines/regression.yml

@@ -0,0 +1,39 @@
+name: regression
+description: Run the tests a change can break, from the coverage map, then explain the failures.
+
+gates:
+  coverage:
+    file: [coverage.tests.yml]
+    message: No coverage.tests.yml. Create one with /qa-test-code-coverage to run only affected tests.
+  testomatio:
+    env: [TESTOMATIO]
+    message: No Testomat.io project. Set TESTOMATIO to the project's API key.
+  local:
+    run: test -z "$REMOTE"
+    message: Tests run on the Testomat.io CI profile. No local log to read.
+  test-command:
+    env: [TEST_COMMAND]
+    message: No test command. Set TEST_COMMAND, e.g. "npx playwright test".
+
+when: [coverage]
+
+env:
+  BASE_BRANCH: ${BASE_BRANCH:-origin/main}
+
+stages:
+  - id: tests
+    when: [testomatio]
+    run: |
+      npx -y @testomatio/reporter run --kind detect --warn \
+        --filter "coverage:file=coverage.tests.yml,diff=$BASE_BRANCH" \
+        ${REMOTE:+--remote "$REMOTE"} ${TEST_COMMAND:+"$TEST_COMMAND"}
+    timeout: 30m
+
+  - id: failures
+    when: [local, test-command]
+    session: triage
+    task: |
+      Read the test run in tests.log. For each failure, say if this change caused it,
+      if it is flaky, or if the test is out of date. /debug-fix-failed-flaky-autotests
+      Do not edit any file. Fail the run if this change caused a failure.
+    inputs: [tests.log]

package/pipelines/web-testing.yml

@@ -0,0 +1,50 @@
+name: web-testing
+description: Review a pull request, test the change in a browser with Explorbot, explain what broke.
+
+gates:
+  staging:
+    env: [EXPLORBOT_URL]
+    message: No staging URL. Set EXPLORBOT_URL to test in a browser.
+  browser:
+    run: ls "${PLAYWRIGHT_BROWSERS_PATH:-$HOME/.cache/ms-playwright}" | grep -q chromium
+    message: No browser. Run npx playwright install --with-deps chromium.
+  explorbot-ai:
+    env: [EXPLORBOT_AI_PROVIDER]
+    message: Explorbot has no AI provider. Set EXPLORBOT_AI_PROVIDER and its key.
+
+env:
+  EXPLORBOT_OUTPUT: ${PIPELINE_DIR}/explorbot
+  EXPLORBOT_NO_BANNER: "1"
+
+stages:
+  - id: review
+    session: qa
+    task: |
+      Review this pull request as a QA engineer. /qa-review-pr
+      Write the user-facing scenarios worth checking in a browser to scenarios.md.
+    outputs: [scenarios.md]
+
+  - id: write-plan
+    session: qa
+    when: [staging]
+    task: |
+      Turn scenarios.md into an Explorbot test plan for ${EXPLORBOT_URL}. /explorbot-plan
+      Write the plan to plan.md. Keep only scenarios a browser can check.
+    inputs: [scenarios.md]
+    outputs: [plan.md]
+
+  - id: explore
+    when: [staging, browser, explorbot-ai]
+    run: npx -y explorbot test "$PIPELINE_DIR/plan.md" '*'
+    inputs: [plan.md]
+    outputs: [explorbot/]
+    timeout: 30m
+
+  - id: results
+    session: qa
+    when: [staging, browser, explorbot-ai]
+    task: |
+      Explorbot results are under explorbot/. Find its session report and read it.
+      Say which failed scenarios are real defects in this change and which are test noise.
+      Fail the run if any is a real defect.
+    inputs: [plan.md, explorbot/]

package/prompt/testomat.io.ts

@@ -39,18 +39,18 @@ export function testomatio(options: TestomatioOptions): string {
 
 function dynamicData(tms: TmsAccess): string {
   if (tms === "mcp-proxy") {
-    return "Get them through the `mcp` tool: search it for the operation you need, then call that operation. The most common reads are also registered as tools of their own; use those directly when they fit.";
+    return "Get them through the Testomat.io tools, one per entity (`tests`, `runs`, `testruns`, `issues`, …); pick the operation with its `command` param. The `mcp` tool searches them when the name is unclear.";
   }
   if (tms === "cli-only") {
     return "There are no Testomat.io tools in this session. Get them from the REST API: `curl` with the `TESTOMATIO` token as the Authorization header against `$TESTOMATIO_URL/api/v2`. Keep to documented endpoints; never invent paths or parameters.";
   }
-  return "Get them through the `testomatio-<slug>` MCP tools, one set per project.";
+  return "Get them through the `testomatio-<slug>` MCP tools, one set per project and one tool per entity; pick the operation with its `command` param.";
 }
 
 /**
- * `mcp-proxy`: one `mcp` tool with search and call. `cli-only`: no tools at
- * all; `check-tests` and REST through the shell. `mcp-direct`: every operation
- * is its own tool, prefixed `testomatio-<slug>`; the desktop app's one-shot mode.
+ * `mcp-proxy`: one tool per entity plus the `mcp` search tool. `cli-only`: no
+ * tools at all; `check-tests` and REST through the shell. `mcp-direct`: one tool
+ * per entity, prefixed `testomatio-<slug>`; the desktop app's one-shot mode.
  */
 export type TmsAccess = "mcp-direct" | "mcp-proxy" | "cli-only";
 

package/skills/skills.lock.json

@@ -3,7 +3,7 @@
     {
       "source": "testomatio/skills",
       "ref": null,
-      "sha": "0d4a8add8c39301979a171dd42804823d38e11de",
+      "sha": "f971b5264682260d0257e2e21f1dfa20836fe8d3",
       "folder": "testomatio",
       "skills": [
         "automate-manual-test-cases",
@@ -76,7 +76,7 @@
     {
       "source": "microsoft/playwright-cli/tree/main/skills/playwright-cli",
       "ref": null,
-      "sha": "b85c7a736bb473bf55b584e54a09ffa698d6d871",
+      "sha": "b1a5903c5b633b8c9f843ad7b629c2a78437040c",
       "folder": "playwright",
       "skills": [
         "playwright-cli"

package/skills/testomatio/test-management/detect-useless-tests/SKILL.md

@@ -3,7 +3,7 @@ name: detect-useless-tests
 description: Find useless tests within one testing level (unit, e2e, manual) and list them by area, file, and line for review. Use when asked "which tests can we delete?", "find useless tests", or "what in our suite is not worth keeping?".
 ---
 
-# Detect Useless Manual Tests
+# Detect Useless Tests
 
 Go through tests of the same level (unit, e2e, manual) and detect useless ones.
 User must provide exact locations of tests to check to identify the level of tests in pyramid.

package/skills/testomatio/test-management/improve-test-cases/SKILL.md

@@ -24,7 +24,7 @@ Analyze and improve existing markdown manual test cases to make them clearer for
 
 ## Step 1: Locate Test Files
 
-- Find markdown test files (`.test.md` or `.md`) in common locations: `./manual-tests`, `./tests/manual`, `./docs/tests`.
+- Find markdown test files (`.test.md` or `.md`) in common locations: `./test-cases`, `./tests/manual`, `./docs/tests`.
 - If none found, scan the whole project for `.md` files with test case content.
 - If still none, ask the user for the test directory path.
 

package/skills/testomatio/test-management/qa-test-code-coverage/SKILL.md

@@ -36,7 +36,7 @@ Analyze the project's tests — manual markdown cases and automated e2e tests
   - Project Overview — languages, frameworks, complexity (drives the subagent split in Step 4).
 - Map whatever exists: both kinds go into one coverage file; a single kind is fine too.
 - ❓ If the scan finds no tests at all (it checks the `.testeiya/` cache too), ask the user:
-  1. Pull manual cases from Testomat.io — have `sync-test-cases-with-tms` pull into the cache: `npx check-tests pull -d .testeiya/manual-tests`, add `.testeiya/` to `.gitignore` if missing, re-run the scan.
+  1. Pull manual cases from Testomat.io — have `sync-test-cases-with-tms` pull into the cache: `npx check-tests pull -d .testeiya/test-cases`, add `.testeiya/` to `.gitignore` if missing, re-run the scan.
   2. Clone the automated tests repo: `git clone <url> .testeiya/e2e-tests`, add `.testeiya/` to `.gitignore` if missing, re-run the scan.
   3. Point to a directory the scan missed, then re-run the scan there.
   4. Stop.
@@ -165,7 +165,7 @@ npx @testomatio/reporter run --kind manual \
 - Coverage gaps — source features no test maps to. On approval, propose new cases (delegate to `qa-write-test-cases`).
 - Dead tests — tests whose features no longer exist in source.
 - Answer questions like "do we have tests for X?" from the inventory.
-- Editing pulled manual cases: edit them in `.testeiya/manual-tests/` and push back with `sync-test-cases-with-tms`.
+- Editing pulled manual cases: edit them in `.testeiya/test-cases/` and push back with `sync-test-cases-with-tms`.
 
 ## References
 

package/skills/testomatio/test-management/qa-write-test-cases/SKILL.md

@@ -61,7 +61,7 @@ Information sources:
 - Design mockups (Figma, Miro, etc.)
 - Existing test cases (TestRail, Testomat.io, etc.)
 - Source code:
-  - manual test files: `.test.md` or `.md` in folders like `manual-tests`, `tests`, `manual`, `qa`, `spec`
+  - manual test files: `.test.md` or `.md` in folders like `test-cases`, `tests`, `manual`, `qa`, `spec`
   - automated test files (spec, test, cy files, etc.)
   - project structure
 
@@ -218,8 +218,8 @@ If the user originally asked only for a checklist, first ask: "Do you want to ge
 Where to store test cases:
 
 - Empty or manual-tests-only workspace → project root
-- End-to-end testing project → `manual-tests/` directory
-- Any other case → `.testeiya/manual-tests/` (ensure `.testeiya/` exists and is git-ignored)
+- End-to-end testing project → `test-cases/` directory
+- Any other case → `.testeiya/test-cases/` (ensure `.testeiya/` exists and is git-ignored)
 
 Generation rules:
 

package/skills/testomatio/test-management/scan-automation-project/SKILL.md

@@ -36,7 +36,7 @@ All persistent QA metadata lives in `.testeiya/` in the project root.
 - `<name>/`: a linked or cloned external project, named after its source. Read-only reference.
 - `requirements/`: user stories and acceptance criteria (pdfs, docs, images).
 - `docs/`: feature explanations, test planning and strategy files. Prose for humans, never data dumps.
-- `manual-tests/`: markdown test cases pulled from Testomat.io.
+- `test-cases/`: markdown test cases pulled from Testomat.io.
 - `auto-tests/`: references to the relevant automated (e2e) tests.
 - `exploratory/`: explorbot setup.
 - `project-info.json`: the project's settings as Testomat.io reports them, when cached.
@@ -53,13 +53,13 @@ Rules:
 | This project has | Store pulled data in |
 | ------------------ | ---------------------- |
 | **Source code** (`src/` folder) or **big project** | `.testeiya/…` |
-| **Only test infrastructure** (e2e dirs like `tests/`, `playwright/`, `cypress/` but no `src/`) | `manual-tests/` or `e2e-tests/` |
-| **Empty / manual-only** | `manual-tests/` |
+| **Only test infrastructure** (e2e dirs like `tests/`, `playwright/`, `cypress/` but no `src/`) | `test-cases/` or `e2e-tests/` |
+| **Empty / manual-only** | `test-cases/` |
 
 Detection logic:
 1. Has `src/` folder or is a monorepo? → Use `.testeiya/`
-2. Has e2e test dirs (`tests/`, `playwright/`, `cypress/`, `e2e/`)? → Use tracked folder (`manual-tests/`, `e2e-tests/`)
-3. Otherwise → Default to `manual-tests/`
+2. Has e2e test dirs (`tests/`, `playwright/`, `cypress/`, `e2e/`)? → Use tracked folder (`test-cases/`, `e2e-tests/`)
+3. Otherwise → Default to `test-cases/`
 
 - The rule covers *pulled* data only. Output a skill *produces* and the user wants — a `coverage.*.yml`, new `*.test.md` files — goes in the repo as normal.
 - On a source repo with no manual tests, this skill changes no tracked file: it only creates the self-ignored `.testeiya/` directory.
@@ -107,7 +107,7 @@ A `*.test.md` file is a suite. Each test inside it is a `<!-- test ... -->` bloc
 - `type: automated`: a **reference** to an automated test (see below).
 - No `type:` line at all: treat as manual. This is common, so never count manual tests by grepping for `type: manual`; it silently undercounts.
 
-Know the counts before you answer anything about project scope, coverage or progress. Read them straight from the files; this mirrors how Testomat.io parses them. `find .` also looks inside `.testeiya/manual-tests/`, so a re-run after a pull finds the cached cases instead of reporting "no manual tests":
+Know the counts before you answer anything about project scope, coverage or progress. Read them straight from the files; this mirrors how Testomat.io parses them. `find .` also looks inside `.testeiya/test-cases/`, so a re-run after a pull finds the cached cases instead of reporting "no manual tests":
 
 ```bash
 # one line per suite or test: SUITE <title>, or <type> <title>
@@ -127,7 +127,7 @@ find . -name "*.test.md" -exec awk '
 
 Pipe the output into `grep -c '\[manual\]'` or `grep -c '\[automated\]'` to count one kind.
 
-- If the only `.test.md` files are under `.testeiya/manual-tests/`, say so in the inventory: they came from Testomat.io, not from this repo.
+- If the only `.test.md` files are under `.testeiya/test-cases/`, say so in the inventory: they came from Testomat.io, not from this repo.
 - A source checkout with no `*.test.md` files has nothing to count. Say so; do not estimate.
 
 ### Automated tests
@@ -186,7 +186,7 @@ Return one structured markdown result directly. **Do NOT save to a file.**
 ## Test Inventory
 
 - **Automated Tests:** 10 files (Playwright)
-- **Manual Tests:** 37 cases (`.testeiya/manual-tests/`, pulled from Testomat.io)
+- **Manual Tests:** 37 cases (`.testeiya/test-cases/`, pulled from Testomat.io)
 - **Automated References:** 12 (implementation lives in another repository)
 
 ### Manual Tests (20 of 37 shown)

package/skills/testomatio/test-management/sync-test-cases-with-tms/SKILL.md

@@ -38,18 +38,18 @@ Downloads test scenarios from Testomat.io and saves them as local Markdown files
 
 Directory selection — if the `testDir` input is provided or the user passes `-d <path>`, use that path. Otherwise:
 - Workspace is empty or for manual tests only: pull to root.
-- End-to-end testing project: pull to the `manual-tests` directory.
-- Any other case: pull to `.testeiya/manual-tests` (ensure `.testeiya/` exists and is gitignored).
+- End-to-end testing project: pull to the `test-cases` directory.
+- Any other case: pull to `.testeiya/test-cases` (ensure `.testeiya/` exists and is gitignored).
 
 Cache-folder rules:
-- Default pull target is the gitignored cache `.testeiya/manual-tests/`. Add `.testeiya/` to the project `.gitignore` if it is not there yet.
-- **Pulled cases must never land in a tracked folder** (`manual-tests/`, etc.) — that pollutes the repo.
+- Default pull target is the gitignored cache `.testeiya/test-cases/`. Add `.testeiya/` to the project `.gitignore` if it is not there yet.
+- **Pulled cases must never land in a tracked folder** (`test-cases/`, etc.) — that pollutes the repo.
 - Being gitignored does not block editing the files or pushing them back.
 - If the repo already keeps its `*.test.md` files in a tracked folder, don't pull — work with them in place, or pass `-d <that folder>` for an in-place refresh.
 - This matches `scan-automation-project`, which pulls the *code* into `.testeiya/code/` when it runs inside a manual-tests repo.
 
 ```bash
-npx check-tests pull -d .testeiya/manual-tests
+npx check-tests pull -d .testeiya/test-cases
 ```
 
 - To pull only specific suites (user names a suite or gives suite IDs): `npx check-tests pull --suite-ids "@S12345678,@S87654321"`.
@@ -62,7 +62,7 @@ Uploads local Markdown tests to Testomat.io.
 Pre-push file filtering — push only test case files, never project docs or requirements:
 - Include files matching `*.test.md`, or Markdown files with valid `<!-- test ... -->` blocks.
 - Ignore all other Markdown (`README.md`, `CHANGELOG.md`, documentation).
-- If test cases live alongside other files, copy or move the test files into `.testeiya/manual-tests/` first.
+- If test cases live alongside other files, copy or move the test files into `.testeiya/test-cases/` first.
 
 Pre-push validation:
 1. At least one `*.test.md` file exists.
@@ -85,13 +85,13 @@ labels: ...
 npx check-tests push --files login.test.md checkout.test.md
 
 # Testeiya cache folder
-npx check-tests push -d .testeiya/manual-tests
+npx check-tests push -d .testeiya/test-cases
 ```
 
 - **When the files to push are known** (e.g. just produced by `qa-write-test-cases` / `improve-test-cases`), **pass them explicitly via `--files`** (alias `-f`). Without `--files` the CLI falls back to the default glob `**/*.test.md`, which may pick up unrelated files.
 - Quote glob patterns. Paths resolve relative to `--dir`.
-- Use `-d` when `.testeiya` or `manual-tests` directories exist.
-- **Push only the test cases directory** (e.g. `.testeiya/manual-tests`, not `.testeiya/`).
+- Use `-d` when `.testeiya` or `test-cases` directories exist.
+- **Push only the test cases directory** (e.g. `.testeiya/test-cases`, not `.testeiya/`).
 - More push options and examples: [TESTOMATIO_CLI.md](./references/TESTOMATIO_CLI.md).
 
 ## Summary Output

package/skills/testomatio/test-management/sync-test-cases-with-tms/references/TESTOMATIO_CLI.md

@@ -85,11 +85,11 @@ npx check-tests pull [options]
 # Export tests to current directory
 npx check-tests pull
 
-# Export tests to manual-tests folder
-npx check-tests pull -d manual-tests
+# Export tests to test-cases folder
+npx check-tests pull -d test-cases
 
 # Keep source structure
-npx check-tests pull -d manual-tests --keep-structure
+npx check-tests pull -d test-cases --keep-structure
 
 # Pull specific suites only
 npx check-tests pull --suite-ids "@S12345678,@S87654321"
@@ -117,7 +117,7 @@ npx check-tests push
 npx check-tests push -f docs/login.test.md docs/checkout.test.md
 
 # Glob (quoted)
-npx check-tests push --files "manual-tests/**/*.test.md"
+npx check-tests push --files "test-cases/**/*.test.md"
 
 # Multiple globs
 npx check-tests push -f "smoke/**/*.test.md" "regression/**/*.test.md"