testrail

Bidirectional sync between Playwright tests and TestRail test management.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "testrail" with this command: npx skills add alirezarezvani/claude-skills/alirezarezvani-claude-skills-testrail

TestRail Integration

Bidirectional sync between Playwright tests and TestRail test management.

Prerequisites

Environment variables must be set:

If not set, inform the user how to configure them and stop.

Capabilities

  1. Import Test Cases → Generate Playwright Tests

/pw:testrail import --project <id> --suite <id>

Steps:

  • Call testrail_get_cases MCP tool to fetch test cases

  • 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' })

  • Generate test files grouped by section

  • Report: X cases imported, Y tests generated

  1. Push Test Results → TestRail

/pw:testrail push --run <id>

Steps:

  • Run Playwright tests with JSON reporter: npx playwright test --reporter=json > test-results.json

  • Parse results: map each test to its TestRail case ID (from annotations)

  • Call testrail_add_result MCP tool for each test:

  • Pass → status_id: 1

  • Fail → status_id: 5, include error message

  • Skip → status_id: 2

  • Report: X results pushed, Y passed, Z failed

  1. Create Test Run

/pw:testrail run --project <id> --name "Sprint 42 Regression"

Steps:

  • Call testrail_add_run MCP tool

  • Include all test case IDs found in Playwright test annotations

  • Return run ID for result pushing

  1. Sync Status

/pw:testrail status --project <id>

Steps:

  • Fetch test cases from TestRail

  • Scan local Playwright tests for TestRail annotations

  • Report coverage: TestRail cases: 150 Playwright tests with TestRail IDs: 120 Unlinked TestRail cases: 30 Playwright tests without TestRail IDs: 15

  1. Update Test Cases in TestRail

/pw:testrail update --case <id>

Steps:

  • Read the Playwright test for this case ID

  • Extract steps and expected results from test code

  • Call testrail_update_case MCP tool to update steps

MCP Tools Used

Tool When

testrail_get_projects

List available projects

testrail_get_suites

List suites in project

testrail_get_cases

Read test cases

testrail_add_case

Create new test case

testrail_update_case

Update existing case

testrail_add_run

Create test run

testrail_add_result

Push individual result

testrail_get_results

Read historical results

Test Annotation Format

All Playwright tests linked to TestRail include:

test('should login successfully', async ({ page }) => { test.info().annotations.push({ type: 'testrail', description: 'C12345', }); // ... test code });

This annotation is the bridge between Playwright and TestRail.

Output

  • Operation summary with counts

  • Any errors or unmatched cases

  • Link to TestRail run/results

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

aws-solution-architect

No summary provided by upstream source.

Repository SourceNeeds Review
General

social-media-analyzer

No summary provided by upstream source.

Repository SourceNeeds Review
General

senior-frontend

No summary provided by upstream source.

Repository SourceNeeds Review
General

senior-backend

No summary provided by upstream source.

Repository SourceNeeds Review