error-injection-tester

You can test web application resilience by injecting controlled network failures like offline mode and slow 3G conditions. This systematically validates error boundaries, verifies fallback behaviors, and records screenshots to support robust recovery and UX improvements.

Yes, you can simulate API error responses and block critical resources like CSS, JS, and images. This intercepts requests to test graceful degradation, verifying how the web application UI handles missing dependencies and failed data fetches.

You verify JavaScript error boundaries by injecting exceptions and unhandled rejections into the loaded target page. The tester logs console output to evaluate whether the web application captures errors properly and renders appropriate fallback UI components.

Yes, resilience testing supports localStorage quota scenarios in Chromium-based browsers. It injects storage limits to evaluate recovery strategies and verify that storage-bound web applications handle quota exceeded errors gracefully without crashing.

Yes, you need a connected and responding Playwright MCP server, a Chromium-based browser, and a loaded target page. These prerequisites allow the tester to instrument the web application and capture a baseline before injecting controlled failures.