← ClaudeAtlas

xlsx-testcaseslisted

Use when team maintains test cases in XLSX (tester-owned source of truth) and needs conversion to Maestro YAML, Detox, or Markdown specs, or two-way sync with Azure DevOps Test Plans.
tuannv14/claude-team-toolkit · ★ 1 · Testing & QA · score 70
Install: claude install-skill tuannv14/claude-team-toolkit
# /xlsx-testcases — bridge tester xlsx ↔ runnable tests Keeps xlsx as **source of truth** for test cases (testers' familiar tool), generates runnable artifacts on demand, and syncs to Azure DevOps Test Plans. Deps: `anthropic-skills:xlsx` (delegate parsing), `jq`, `python3`. ADO sync uses `/azure-devops` skill (multi-profile). ## Overview Bridges xlsx-based test case authoring (testers' familiar tool) with runnable test specs. Generates Maestro YAML / Detox / Markdown on demand and syncs to Azure DevOps Test Plans. xlsx remains the **source of truth** — generated artifacts are derivable. ## When to Use - QA team maintains test cases in xlsx (no migration possible) - Need runnable artifacts (Maestro YAML, Detox, Markdown checklists) - Two-way sync with Azure DevOps Test Plans - Coverage gap reports (TCs in xlsx not yet automated) ## When NOT to Use - Test cases live in code already → no need for this bridge - One-off conversion → use `anthropic-skills:xlsx` directly - Real-time test execution → this is scaffolding, not a runner - Non-tabular test specs (BDD `.feature` files) → use Cucumber / Gherkin tooling ## Schema mapping Per-workbook schema at `<xlsx-folder>/.testcase-schema.yml` (committed): ```yaml sheet: "Test Cases" # or "*" for all sheets header_row: 2 columns: id: "TC ID" # required, unique module: "Module" title: "Title" # required steps: "Steps" # multi-line cell expected: "Expected R