Skip to content

BrowserDebug 1.0.0

Choose a tag to compare

@Taurusxw Taurusxw released this 13 Jul 03:28
· 8 commits to main since this release

BrowserDebug v1.0.0

BrowserDebug v1.0.0 is the first public release of the Windows-first local
control plane for frontend, backend/API, web page, and unpacked Chrome MV3
extension testing.

Highlights

  • One CLI owns service startup, browser execution, typed tests, evidence, and
    cleanup for each run.
  • Playwright Chrome for Testing and Puppeteer-controlled real Chrome lanes.
  • Persistent shared general and named profiles, plus freshly confirmed
    isolated profiles and external-write authority.
  • Declarative page, API, command, authentication, upload/download, device,
    permission, network, and MV3 extension workflows.
  • Authenticated loopback graphical console with project registration, live and
    historical runs, diagnostics, logs, verified artifacts, sensitive reveal,
    profile management, and authenticated Stop.
  • Strict Artifact v1/v2 readers, evidence-linked diagnostics, bounded recovery,
    Windows Job Object ownership, and exact cleanup reporting.

Installation

git clone https://github.com/Taurusxw/BrowserDebug.git
cd BrowserDebug
npm install
. .\scripts\resolve-extension-runtime-env.ps1
.\scripts\run-browserdebug.ps1 doctor --json
.\scripts\run-browserdebug.ps1 console

Acceptance

  • Fresh Windows suite: 840 total, 838 passed, 0 failed, 2 documented
    platform skips.
  • Desktop 1280x720 and mobile 390x844 graphical-console QA passed.
  • Real full-stack, API, web page, MV3, Playwright, Puppeteer, named profile,
    screenshot reveal, authenticated Stop, and cleanup flows passed.
  • No real external write was performed during validation.

See release acceptance for the publication gate and residual
platform limits.