error

Capture browser errors with screenshots and element snapshots during end-to-end testing.

2.3k|331|Updated Jun 3, 2024
One-click install
npx skills add https://github.com/crbnos/carbon --skill error-crbnos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error
Source: https://github.com/crbnos/carbon/tree/main/.ai/skills/error
Command: npx skills add https://github.com/crbnos/carbon --skill error-crbnos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill captures and reports browser errors that occur during end-to-end testing, ensuring you have the necessary diagnostics to troubleshoot issues efficiently.

Core Features & Use Cases

  • Error Capture: Takes screenshots and element snapshots of the current browser page when an error occurs.
  • Use Case: When an end-to-end test encounters a failure, this Skill can be invoked to capture the necessary information for debugging.

Quick Start

Run the error skill when encountering a failure during end-to-end testing to capture diagnostics.

Frequently Asked Questions about error

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

FAQPage Schema
How do I capture browser errors during e2e testing?

To capture browser errors during e2e testing, you can invoke this Skill upon test failure to automatically take screenshots and element snapshots of the current page for debugging.

What is the best way to debug failed end-to-end tests in web applications?

Debugging failed end-to-end tests requires capturing browser diagnostics. This Skill logs screenshots and element snapshots of the exact state when a web application test failure occurs.

How do I take screenshots and element snapshots when an e2e test fails?

You can take screenshots and element snapshots when an e2e test fails by running this Skill during the failure event to capture the necessary browser state for troubleshooting.

Do I need browser access to capture browser diagnostics for test debugging?

Yes, capturing browser diagnostics for test debugging requires browser access and execution during test failures to accurately capture and log the current page state.

When should I trigger browser error capture during web application testing?

You should trigger browser error capture during web application testing when an end-to-end test encounters a failure, ensuring you capture the necessary page diagnostics for troubleshooting.