Open-source API automation · flow canvas · Cursor MCP

Qualitest 质衡

After you change code, write and run flows in Cursor

Import APIs → write a test flow → run it → fix failures in chat. Or use the full Web debugger and canvas; ingest via IntelliJ or MCP (any stack).

Ingest Debug Canvas AI MCP
Loop: ingest → debug → canvas → AI → MCP

5-minute Quick Start

Clone the main repo and bring the stack up with Compose. Open http://localhost , sign in as admin / admin123 . For production, change the default password and token.secret .

Windows
PS> scripts\quick-start.bat
Linux / macOS
$ chmod +x scripts/quick-start.sh && ./scripts/quick-start.sh

For the demo target, see qualitest-demo-mall ; deployment details in docs/deploy.en.md .

Closed loop in one project

Where APIs come from, how you debug them, how you chain them, and who helps design — without juggling tools.

  1. 01 API ingest

    IntelliJ plugin (Java) or MCP import_apis (any stack)

  2. 02 API debugger

    Multi-env switching and auth injection in-project

  3. 03 Test flows

    Canvas nodes for login, business steps, and asserts

  4. 04 AI Diff

    Edit flows in natural language; preview Diff before merge

  5. 05 MCP

    Write=build the flow · run=hit Run; fewer hops for backend and frontend

  • API debugger
    API console: send request, get 200
  • Test flows
    Test-flow canvas at a glance
  • AI Diff
    AI flow edit: stop at Diff, merge only after confirm

MCP · Build and run flows in Cursor after you change code

Write = build the test flow; run = hit Run. Read-only by default; with gates on, create-then-verify in one chat. Backend & frontend scenarios: docs/mcp.en.md .

  • Write

    Cursor builds / edits the canvas; successful submit persists. Open Web canvas syncs over SSE. Backend authors the chain after an API change; frontend mirrors the page path first.

    MCP write: Cursor builds the flow; Web canvas syncs over SSE
    1. Enable Allow MCP auto-write in project settings and save
    2. Reconnect MCP, then create_flow / submit_*
    3. Confirm the Web canvas synced over SSE
  • Run

    Cursor hits Run; failures return to the chat so you can fix them there. Both sides hop to the browser less.

    MCP run: Cursor calls run_test_flow; failures return to chat
    1. Also enable Allow MCP auto-run, save, then reconnect
    2. run_test_flow against the latest graph in the DB
    3. On failure, get_run_failure and fix in chat

Ecosystem

Three separate repos that work together; the main repo stays free of demo-target code. GitHub is canonical; Gitee is a read-only mirror.

  • qualitest Core platform · backend + Web GitHub Gitee
  • qualitest-demo-mall API demo target · own Compose GitHub Gitee
  • qualitest-intellij-plugin IntelliJ plugin · Java API sync (optional) GitHub Gitee