qa-detect-network-errors

Capture HTTP error responses and failed network requests during Playwright browser navigation.

Updated May 22, 2026

Search Tags:#playwright #browser testing #qa automation #network errors #http responses #failed requests

Ready to run

npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-detect-network-errors

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-detect-network-errors
Source: https://github.com/Luqman-Ud-Din/blackbox-qa-agent/tree/main/skills/qa-detect-network-errors
Command: npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-detect-network-errors

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify network failures that appear during page navigation so broken backend calls do not get missed during QA runs.

Core Features & Use Cases

HTTP Error Detection: Flags 4xx and 5xx responses returned by pages under test.
Request Failure Capture: Records failed requests and reports the failure reason for debugging.
QA Workflow Fit: Useful for audit-style browser testing where you need to catch missing APIs, server errors, or broken static assets as part of an automated pass.

Quick Start

Run this skill on a page test so it captures network requests during navigation and reports any failed or error responses.

Frequently Asked Questions about qa-detect-network-errors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect network errors and failed HTTP requests during Playwright browser testing?▼

This Skill detects network errors during Playwright browser testing by capturing HTTP responses and failed requests during navigation, then filtering ignored URLs to classify 4xx, 5xx, and request failures for debugging.

What is the best way to catch 4xx and 5xx HTTP responses in QA automation?▼

The best way to catch 4xx and 5xx HTTP responses in QA automation is to apply an audit-style Playwright test that collects network requests before and after page navigation and flags error status codes.

Can I use this to find broken backend calls and missing APIs across different viewports?▼

Yes, you can use this to find broken backend calls across different viewports because it inspects page loads across supported routes and viewports to capture missing APIs, server errors, and broken static assets.

How do I record the failure reason for failed network requests during page navigation?▼

To record the failure reason for failed network requests during page navigation, you run a Playwright-based QA audit that captures request failures and reports the underlying failure reason for debugging.

Does network request collection require filtering specific URLs before classifying HTTP errors?▼

Yes, network request collection requires filtering ignored URLs before classifying HTTP errors, ensuring that only relevant 4xx, 5xx, and request failures are flagged during the browser navigation audit.