v0.7.1 — client-initiated fetch aborts are not resource faults - #9

Process completed with exit code 1.

AssertionError: README.md Status section must mention v0.7.1: expected '# ReproCase\n\n[](https://github.com/geyutu6755/ReproCase/actions/workflows/ci.yml) + [](https://geyutu6755.github.io/ReproCase/) + [](LICENSE) + + **Automated website fault detection & reproduction.** ReproCase scans a website in a real browser, + finds faults that have objective evidence, independently re-verifies every fault, and emits + reproducible Playwright regression tests plus reports written for humans *and* AI coding assistants. + + - 中文文档：[README.zh-CN.md](README.zh-CN.md) + + ## What it detects + + | Fault | Evidence collected | Default severity | + | --- | --- | --- | + | Uncaught JS exceptions (incl. unhandled promise rejections) | message, stack, exact click path, screenshot, browser trace | high | + | Page load failures (HTTP ≥ 400 or navigation error) | status code / error text, screenshot | high | + | First-party resource failures (scripts, images, CSS, ...) | resource URL, status / net error, screenshot | medium | + | Broken internal links | target URL, status, all linking pages | medium | + | Horizontal overflow (desktop + mobile viewports) | scrollWidth vs clientWidth, offending elements, screenshot | low | + | Console errors | message, page, reproducibility | suspected (informational) | + + Every finding is labelled **verified** (reproduced in independent browser runs) or **suspected** + (observed once but not proven reproducible). ReproCase never invents results, never judges + business logic, and always lists what it did **not** check. + +  +  +  + + ## Quick start + + ```bash + # Try it in ~30 seconds — scans the bundled demo site (4 planted faults): + git clone https://github.com/geyutu6755/ReproCase.git + cd ReproCase && npm install && npx playwright install chromium # npm install auto-builds dist/ + npx reprocase demo # writes reprocase-demo-report/report.html and opens it + ``` + + Start a real project: + + ```bash + npx reprocase init # writes a starter reprocase.config.json (refuses to overwrite) + npx reprocase doctor # environment check: Node, Chromium, config, target, writability + npx reprocase scan # scan the configured entry, write the full report bundle + npx reprocase scan --url http://localhost:3000/ --out my-report + npx reprocase compare before/result.json after/result.json # new / resolved / persistent + ``` + + > Exit codes: `0` no findings at/above threshold · `1` findings exist · `2` scan failed + > (bad config, entry unreachable). CI-friendly — see [docs/cli.md](docs/cli.md). + + [**Live demo report**](https://geyutu6755.github.io/ReproCase/) — generated by the CI pipeline + against the bundled demo site on every push to `main`. + + ## What a scan produces + + ``` + my-report/ + ├── report.html self-contained offline HTML report (also index.html) + ├── result.json machine-readable scan result + ├── issues.md GitHub-Issue markdown covering all findings + ├── issues/<id>.md one ready-to-paste issue per finding + ├── generated-tests/ runnable Playwright reproduction tests + config + README + └── artifacts/ + ├── screenshots/ evidence screenshots + └── traces/ Playwright traces (playwright show-trace) + ``` + + The generated Playwright tests **assert the fault is still present**: they pass while the bug + exists (proving stable reproduction) and fail once you fix it — the failure tells you to swap in + the commented-out "after fix" as