harness-browser-test

To run headless browser tests, launch a dev server and use headless Chromium to execute scripted interactions like click, fill, and scroll, then capture screenshots. This automates UI verification and produces a textual pass/fail report for debugging.

Yes, you can use Playwright to automate e2e testing by starting your local dev server and running headless Chromium to perform deterministic actions. It accepts an actions JSON file to drive interactions and returns console errors and screenshot paths.

Yes, Node and Playwright are required dependencies to automate browser interactions. You also need the optional ability to start a dev server if you want to test local applications, along with an actions JSON file to define the test steps.

During headless Chromium browser testing, you can execute deterministic actions such as click, fill, wait, evaluate, and scroll. These actions are driven by an actions JSON file to simulate user flows and verify web application behavior.

To collect console errors and visual evidence during e2e-testing, run headless Chromium to execute scripted interactions and capture screenshots. The process outputs a textual report listing console errors and provides screenshot paths for visual proof.

The best way to catch regressions early in CI workflows using browser-testing is to run smoke tests on each push. Launch a dev server, execute deterministic actions with headless Chromium, and save visual evidence like screenshots to identify failures quickly.