testrail

Topics in the source

• TestRail Integration
• Prerequisites
• Capabilities
• 1. Import Test Cases → Generate Playwright Tests
• 2. Push Test Results → TestRail
• 3. Create Test Run
• 4. Sync Status
• 5. Update Test Cases in TestRail

Bidirectional sync between Playwright tests and TestRail test management. Environment variables must be set: TESTRAILURL — e.g., https://your-instance.testrail.io TESTRAILUSER — your email TESTRAILAPIKEY — API key from TestRail If not set, inform the user how to configure them and stop. The TestRail MCP server is not auto-registered (issue #978). pw-testrail was removed from the plugin's .mcp.json because it failed to connect for every user (the plugin ships no nodemodules). The testrail MCP tools used below, and the /pw:testrail command, will fail with "tool not found" until it is enabled manually — see the Integrations section of the plugin's CLAUDE.md (cd integrations/testrail-mcp && npm install, then register the server in your own user/project MCP config). Setting the env vars alone is not sufficient. Steps: 1. Call testrailgetcases MCP tool to fetch test cases 2. For each test case: Read title, preconditions, steps, expected results Map to a Playwright test using appropriate template Include TestRail case ID as test annotation: test.info().annotations.push({ type: 'testrail', description: 'C12345' }) 3. Generate test files grouped by section 4. Report: X cases imported, Y tes

This is an excerpt. Refer to the complete source and its current requirements.