smoke-testing-web-games

Automate web game smoke testing by loading the game in a headless browser, idling, and sending input bursts to detect console errors, uncaught exceptions, or crashes. This verifies runtime health in a real browser environment.

Yes, you can use Playwright with Chromium to check web games for uncaught exceptions. The Skill loads your game in a headless browser and simulates input to catch runtime errors that simulated tests might miss.

You need Node 18+ and Playwright with Chromium installed to run automated browser testing on a web game. These prerequisites allow the script to load HTML files and simulate user input in a headless environment.

Run the smoke test by executing `node scripts/smoke-test.mjs path/to/index.html` in your project directory. This loads your game in a headless browser to monitor for crashes and errors during input simulation.

No, automated smoke testing does not evaluate gameplay quality. It checks runtime health by loading the game in a headless browser and simulating input to detect console errors, uncaught exceptions, or crashes only.

Simulated tests often miss runtime issues that occur in a real browser environment. Running web game smoke tests in a headless browser with simulated input bursts catches console errors and uncaught exceptions that simulated tests miss.