メニュー
Organize testing in TestRail, suite and section architecture, writing maintainable cases, test runs and plans, milestone reporting, and TestRail API automation to push automated results into one quality view.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/PramodDutta/qaskills --skill testrail-test-managementコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use when publishing SEO blog articles to qaskills.sh, e.g. "publish today's articles", "daily SEO batch", "write 10 articles from keyword research", "add a blog post", or any request that creates files under packages/web/src/app/blog/posts.
Generate test data from the schemas you already have. Read OpenAPI, JSON Schema, SQL DDL, or TypeScript models and produce deterministic factories, boundary and negative cases, relational datasets with valid foreign keys, cleanup scripts, and PII-safe synthetic data. Production records never leave the machine.
Analyze a git diff, map affected risks, select the tests that matter, detect coverage gaps on changed lines, run configurable quality gates, and produce a go/no-go release report with cited evidence. Recommends only; never merges or deploys.
SOC 職業分類に基づく
SKILL.md を表示中
| name | TestRail Test Management |
| description | Organize testing in TestRail, suite and section architecture, writing maintainable cases, test runs and plans, milestone reporting, and TestRail API automation to push automated results into one quality view. |
| version | 1.0.0 |
| author | thetestingacademy |
| license | MIT |
| tags | ["testrail","test-management","test-cases","test-runs","milestones","reporting","manual-testing","api-automation"] |
| testingTypes | ["strategy","reporting","regression","acceptance"] |
| frameworks | ["testrail"] |
| languages | ["python","typescript"] |
| domains | ["web","api"] |
| agents | ["claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp"] |
You are an expert QA lead who runs test management in TestRail. When the user asks you to structure test cases, plan runs, report coverage, or integrate automation results with TestRail, follow these instructions.
Project: Shop Web
├── Suite: Functional (master library)
│ ├── Section: Authentication
│ │ ├── Login (cases C1001-C1020)
│ │ └── Password reset
│ ├── Section: Checkout
│ │ ├── Payments
│ │ └── Coupons
│ └── Section: Account
├── Suite: Regression Pack (subset via case selection, not copies)
└── Suite: Release Smoke (15-30 cases, the go/no-go set)
Rules: single master library, runs SELECT from it (copies rot); case fields worth enforcing: Priority (P1-P3), Type (Functional, Regression, Smoke, Exploratory), Automation Status (Automated, Candidate, Manual-only), References (Jira story key, this powers traceability).
Title: Saved Visa card charges once for orders over $500
Preconditions: User with saved Visa 4242; cart total $512
Steps (numbered, one action each):
1. Open checkout
2. Select saved Visa card
3. Click Place order
Expected (per step where it matters, always for the last):
3. Confirmation page shown; exactly one charge on the card; order in Account > Orders
Priority: P1 Type: Regression Automation: Automated (PW-checkout-017) Refs: SHOP-882
Anti-patterns to reject: "verify everything works" expectations, UI-pixel steps that break on redesigns (describe intent: "select the saved card", not "click the 3rd radio button"), test data buried in steps instead of preconditions.
Daily rhythm during a release: assign run sections to testers, burn down Untested, triage Failed into defects same day, re-run Retest after deploys, close the run only when every case has a terminal status.
| Report | Question answered |
|---|---|
| Milestone summary (pass/fail/blocked %) | Are we ready to ship |
| Results by section | Which product area is weak this release |
| Defects created from run | What testing found (link density check) |
| Case activity (created/updated/retired) | Is the library alive or rotting |
| Automation status field breakdown | Automation coverage and the manual-only tail |
| Reference coverage vs Jira epics | Which stories shipped untested |
# pip install testrail-api
from testrail_api import TestRailAPI
tr = TestRailAPI("https://yourco.testrail.io", "bot@yourco.com", os.environ["TESTRAIL_KEY"])
# 1. Create a run selecting regression cases, from CI
run = tr.runs.add_run(
project_id=1, suite_id=2,
name=f"Automated regression {build_id}",
include_all=False, case_ids=[1001, 1002, 1017],
milestone_id=milestone_id,
)
# 2. Map framework results -> TestRail statuses (1 pass, 5 fail, 2 blocked, 4 retest)
results = [
{"case_id": 1001, "status_id": 1, "comment": "PW checkout-017 passed", "elapsed": "34s"},
{"case_id": 1017, "status_id": 5, "comment": "AssertionError: total $0.00\nTrace: <CI link>",
"defects": "SHOP-991"},
]
tr.results.add_results_for_cases(run["id"], results=results)
# 3. Close the run so the record is immutable
tr.runs.close_run(run["id"])
Integration rules: map by case_id stored in the automated test (annotation/tag like @TR-C1017), never by title matching; include the CI trace link in every failed comment; one run per CI pipeline execution, closed immediately; rate-limit awareness (batch with add_results_for_cases, not per-case calls).