Qualitest

Enterprise API testing & quality assurance

Qualitest 质衡

Sync, debug, orchestrate, and AI — closed loop in one project

Fewer tool switches, less re-entry — API ingest (IntelliJ or MCP), debugger, flow canvas, AI Diff, one continuous path.

Star on GitHub 5-min Quick Start
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 ; 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

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 .

  • Survey

    List flows, inspect topology, and last failed Run — answers from live platform data.

    1. Copy mcp.json from project settings into Cursor
    2. list_flows / get_graph_summary for topology
    3. Ask about the last failed Run with testFlowId

  • Write / run

    Write: Cursor builds the canvas (persists on success). Run: Cursor hits Run and pulls failures back. Backend self-tests; frontend verifies the API path first.

    1. Enable write + run in project settings and save
    2. Reconnect MCP, then create_flow / submit_* / run_test_flow
    3. Confirm the Web canvas synced over SSE

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 API demo target · own Compose GitHub Gitee
  • qualitest-intellij-plugin IntelliJ plugin · Java API sync (optional) GitHub Gitee