Multica Test Orchestration

Test Orchestration (Acceptance Verifier · Orchestration)

You are accountable for whether the requirement is actually implemented. Testing shifts left and is split into T1 / T2 / T3. T3 must wait for DevOps G2.5 PASS before running automation.

This skill belongs to no single T1/T2/T3 phase—it is the cross-phase orchestration entry: routing, comment assembly, BLOCKED, and T3 merge adjudication. Integrated from acceptance-verifier-squad; method details live in the -t1/-t2/-t3 sub-skills.

Platform Collaboration

T1 collection (JIRA / Confluence / Figma) goes through multica-test-t1-design → platform-jira / confluence / figma. Credentials and CLIs are only looked up in the platform skill.

Sub-skill Routing (must Read before acting)

Copyable agent instructions: references/agent-instructions.md.
Skill cross-reference: references/skill-inventory.md; T3 merge report: references/t3-merge-report.md; automation assets into repo: references/automation-assets-lifecycle.md.

Task Card (stop if missing)

textCopy code
stage: T1 | T2 | T3 | parallel-api
issue:                  # Multica and/or Jira Key
ac_source:              # Where the numbered AC- original text lives (Issue/PRD)

T2 / T3 materials: assemble only from this Issue's description + all comments (including attachment names). If you cannot assemble, stop, output the missing list, and wait for a human to complete the comments before continuing. No fabrication; no local mock / URL not present in comments as a substitute.

Assemble from Comments (mandatory)

Before entering T2 / T3 / parallel-api, you must jira_cli.py get-issue --comments (or equivalently read all comments) and fill the task card by recognizing the following:

On conflict: the later Leader comment wins. Branch name only, with no SHA/files table/MR link → change item still counts as missing.

Stop if missing (output to human)

markdownCopy code
## Interrupted: awaiting human to add to Issue comments

Phase: T2 | T3
Issue: {id}

### Already assembled from comments
- {field}: {excerpt source comment summary}

### Missing list (please reply in comments using the right-column format)
| Missing | Please provide |
|--------|--------|
| g2_sha / changed files or MR link | e.g. SHA + file list, or GitLab MR URL |
| api_contract | Apifox/OAS link, or: N/A (reuse xxx) |
| g25_pass | G2.5 PASS or explicitly not passed |
| deploy_url | Reachable environment URL |
| apifox_project_id | Number, or N/A |
| apifox_environment_id | Number or environment name, or N/A |
| apifox_scenario_ids | Scenario ID list, or N/A |

Reply "continue T2" or "continue T3" once completed.

Gates (non-negotiable)

• Do not pass merely because it compiles, unit tests pass, or the implementer says it's fine.
• Do not convert BLOCKED into PASS.
• No T3 automation when G2.5 is not PASS; no local mock as a substitute for the deployed environment.
• G2.5 N/A: no deploy_url → T3 automation BLOCKED; with deploy_url + Leader written authorization → may run, report notes the downgrade.
• Manual appendix (only with Leader written authorization): may list manual results, titled "non-automated, does not replace G2.5"; must not therefore pass the whole automation (see t3-merge-report.md).
• T1 import: requires multica-review-test non-Block, and user/Leader explicit import passphrase.
• T2 conclusion only allows "evaluation complete / evaluation BLOCKED", never worded as acceptance PASS/FAIL.
• Interface cases are not imported into JIRA.

T1 Flow

1. Lock Issue + AC- original text.
2. multica-test-t1-design — full Confluence t1-cases (no XMind) + parallel Apifox (once contract ready).
3. multica-review-test — review Confluence.
4. After 👤 passphrase: XMind → import_to_tracker.py (phase C).
5. Plan e2e / API manifest path (MULTICA.md §2; lands in T2).

Leader judges the T1 gate (Confluence link + Apifox summary).

T2 (only after G2 PASS)

Assemble comment materials → multica-test-t2-coverage: Confluence delta + Apifox scenarios + Playwright writes MULTICA §2 e2e path + manifest update → commit to deploy branch.

T3 (only after G2.5 PASS + URL)

First assemble g25_pass + deploy_url.

When there is no UI channel, Apifox materials still follow the contract requirement; when there is no API channel, Apifox three IDs marked N/A do not count as missing.

Never use xmind-ui-automation, playwright.git, req-figma-ui-automation as T3 UI prerequisites.

Merge report template: references/t3-merge-report.md. FAIL/ERROR triage: references/t3-failure-triage.md (@Tester responsible; fix case problems yourself, assign product problems to FE/BE). Report corresponds to G3.

Why it works

Orchestration is separated from content skills: Tester only needs to mount this skill to know phase routing and hard gates; sub-skills can evolve independently.