How to Set Up a Cursor + Playwright Automation Testing Environment

1. Install Cursor and Playwright‑MCP

Use npm install -g @playwright/mcp@latest and npm install -g playwright@latest to install the latest MCP and Playwright packages globally, then run npx playwright install --with-deps to download the required browsers.

2. Configure Cursor

Open Cursor, click the gear icon, locate the “MCP” option, and add a new MCP server configuration with the following JSON:

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": ["@playwright/mcp@latest"]
    }
  }
}

On Windows, the MCP server may fail to start unless the npm package directory is added to the system PATH and the command is wrapped with cmd /c:

{
  "mcpServers": {
    "playwright": {
      "command": "cmd /c npx",
      "args": ["@playwright/mcp@latest"]
    }
  }
}

3. Prepare Test Cases

Place all test‑case files (Excel, JSON, XML, CSV, etc.) in the project root. With Cursor 1.7’s plan mode, the tool asks clarification questions and then generates a complete test plan based on the CSV data.

4. Execute Automated Tests

After reviewing the generated Markdown test plan, run the build operation. Cursor’s Agent mode launches Playwright’s built‑in Chromium, navigates to the local URL, and executes each step automatically. The whole process finishes in about 20 minutes, far quicker than the estimated 4–5 hours.

5. Review Test Report

The generated report (saved as /xxxxx/系统管理测试报告.md) includes test overview, scope, result statistics, detailed step results, screenshots, and identified issues. Example statistics:

| Module | Cases | Passed | Failed | Blocked | Pass Rate |
|--------|-------|--------|--------|---------|-----------|
| Department Management | 2 | 2 | 0 | 0 | 100% |
| User Management | 1 | 1 | 0 | 0 | 100% |
| **Total** | **3** | **3** | **0** | **0** | **100%** |

Key test steps (e.g., adding a department, linking users, assigning departments) are documented with screenshots and validation results, all marked as passed.

6. Issues and Recommendations

Two minor issues were observed:

Intermittent “to‑do” pop‑up blocks actions – resolved by pressing ESC. Suggested improvement: refine modal layering.

Element click timeouts – mitigated with JavaScript clicks. Suggested improvement: enhance element locating and click reliability.

Additional suggestions include batch operations for the “link user” feature and permission controls for “assign department”.

7. Environment Details

Browser: Chromium (Playwright)

Resolution: 1280×720

Tool: Playwright MCP

Screenshot folder:

/Users/fits-vue/Documents/康复系统/FitsAdmin_RTMS/test-screenshots/