Combo: Automated Test Loop (Static Analysis → Sandbox Execution → Browser E2E) Partial

Scenario

After changing code, how do you confirm "nothing got broken"? Three deterministic stages: static analysis (deepcode, catches obvious problems before commit), sandbox execution (swe-rex, actually runs the code in an isolated environment), browser E2E (playwright-mcp, asserts the page's key elements and routes are really reachable). Each tool runs on its own (all entries recorded and individually measured); what's missing is the orchestration and ordering. This combo provides the "static → sandbox → E2E" verification chain with dependency warnings; the combined-chain measurement is pending (see verification evidence).

Combo members

deepcode: static analysis (first gate, pre-commit)

• Download: PyPI package deepcode-hku; China must use the Tsinghua mirror (official direct connection measured borderline at 16s in precheck, may hit the 15s read timeout)
• Version: 2.1.0; Python >= 3.12
• Install:

pip install -i https://pypi.tuna.tsinghua.edu.cn/simple deepcode-hku
deepcode --version

swe-rex: sandbox execution (second gate, run to verify)

• Download: PyPI package swe-rex; China must use the Tsinghua mirror
• Version: 1.4.0; Python >= 3.10; sandbox execution needs Docker (sandbox run not measured in this environment)
• Install:

pip install -i https://pypi.tuna.tsinghua.edu.cn/simple swe-rex==1.4.0
swerex-remote --help

playwright-mcp: browser E2E (third gate, real-page assertions)

• Download: npm package @playwright/mcp; China must use the npmmirror prefix (measured 3s install on 2026-08-29)
• Version: 0.0.79; Node >= 18; first run downloads the browser engine (chromium 113.9MiB)
• Install:

npm_config_registry=https://registry.npmmirror.com npm install -g @playwright/mcp
npx --no-install @playwright/mcp --version
npx --no-install playwright install chromium

Install order

1. Precheck: python3 --version (>= 3.12, hard requirement for deepcode) + node --version (>= 18) + docker --version (swe-rex sandbox).
2. deepcode (pip, static analysis, no port, no background).
3. swe-rex (pip, sandbox uses Docker; without Docker the CLI/library layer still works, the sandbox stage is marked not measured).
4. playwright-mcp (npm + chromium engine ~114MiB; use --headless in GUI-less environments).

Dependency warnings

• Conflicts (all 3 pairs checked, source: site docs):

Local verification record

• possible-compatible 2 pairs: deepcode×playwright-mcp, playwright-mcp×swe-rex (write-surface analysis: playwright-mcp has no shared config write surface — outputs a single file / temporary profile / proxy config)
• Baseline: pip side (deepcode/swe-rex) and npm side (playwright-mcp) are separate ecosystems; venv and npm prefix are naturally isolated
• Versions: Python >= 3.12 (deepcode, stricter than swe-rex's 3.10, precheck against 3.12); Node >= 18 (playwright-mcp); Docker (swe-rex sandbox, not measured)
• Environment: playwright-mcp listens on port 8931 by default (--port can change), chromium engine 113.9MiB disk; swe-rex sandbox spins up a Docker container (resources isolated per container); deepcode has no background process
• China network: pip → Tsinghua mirror; npm → npmmirror; browser engine via the playwright CDN (measured download success 2026-08-29)

Acceptance check (one shot)

Run this block after installing; all green = combo ready; any failure -> back to the matching step in the install walkthrough.

deepcode --version
swerex-remote --help
npx --no-install @playwright/mcp --version

预期输出: DeepCode 2.1.0; swerex-remote prints usage; @playwright/mcp 0.0.79 (chromium engine downloaded). All green = static -> sandbox -> E2E command surface ready

Note: member-level commands measured; sandbox execution needs Docker (not measured, honestly marked).

Verification evidence

Every combo is measured in an isolated environment (smoke + write-surface check); unmeasured items are honestly marked in the text, and measurement dates are listed in the verification section below.

Verified 2026-08-29 · TTL expires — (180 days)