TestRail Integration
This skill enables bidirectional synchronization between Playwright tests and TestRail test management. It can import test cases from TestRail to generate Playwright tests, push test results back to TestRail, create test runs, check sync status, and update TestRail cases from test code.
✨ What it does
- Imports TestRail test cases and generates Playwright tests with TestRail case ID annotations.
- Pushes Playwright test results to TestRail with status mapping (pass, fail, skip).
- Creates TestRail test runs including all test case IDs found in Playwright annotations.
- Reports sync status showing coverage and unlinked cases.
- Updates TestRail test cases based on Playwright test code.
- Uses TestRail MCP tools for all operations.
🎯 When to use it
- When the user mentions 'testrail', 'test management', 'test cases', 'test run', 'sync test cases', 'push results to testrail', or 'import fr
- When you need to generate Playwright tests from existing TestRail test cases.
- When you need to push Playwright test results to TestRail after a test run.
- When you need to create a TestRail test run or check coverage between Playwright and TestRail.
🚀 How to use
Trigger: /pw:testrail
Trigger the skill by mentioning 'testrail' or using the slash command /pw:testrail with subcommands like import, push, run, status, or update. Ensure environment variables TESTRAIL_URL, TESTRAIL_USER, and TESTRAIL_API_KEY are set. Also, the TestRail MCP server must be manually enabled (see Integrations section in CLAUDE.md) or the tools will fail. Example prompts:
/pw:testrail import --project 1 --suite 2
/pw:testrail push --run 123
📄 Output: An operation summary with counts, errors, and links to TestRail runs/results.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/engineering-team/playwright-pro/skills/testrail .claude/skills/testrailSkill source: engineering-team/playwright-pro/skills/testrail/SKILL.md
⚠️ Good to know
Requires environment variables and manual registration of the TestRail MCP server; otherwise, the MCP tools and the /pw:testrail command will fail with 'tool not found'.
❓ FAQ
What environment variables are required?
You need TESTRAIL_URL, TESTRAIL_USER, and TESTRAIL_API_KEY set. If not set, the skill informs you how to configure them and stops.
Why does the /pw:testrail command fail with 'tool not found'?
The TestRail MCP server is not auto-registered due to issue #978. You must manually enable it by following the Integrations section in the plugin's CLAUDE.md, which involves installing dependencies and registering the server in your MCP config.
How are test results mapped to TestRail cases?
Each Playwright test includes an annotation with the TestRail case ID (e.g., 'C12345'). When pushing results, the skill parses these annotations to map each test to its case ID.
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.