debug-failures

Diagnose Biloba spec failures using DOM outlines and failure screenshots.

25|7|Updated Mar 3, 2023
One-click install
npx skills add https://github.com/onsi/biloba --skill debug-failures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-failures
Source: https://github.com/onsi/biloba/tree/main/plugins/biloba/skills/debug-failures
Command: npx skills add https://github.com/onsi/biloba --skill debug-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Biloba failure debugging often hides the reason a spec failed; this skill surfaces on-failure artifacts (DOM outline + failure screenshots) and explains how Biloba adapts outputs for humans, CI, and AI agents.

Core Features & Use Cases

  • On-failure artifacts: Access DOM outlines and screenshots that accompany test failures to quickly identify mismatch points.
  • Environment-aware output: Shows how results adapt for interactive humans, CI pipelines, or AI-assisted tooling (Claude Code, Cursor, etc.).
  • Observability helpers: Details about relevant env vars (BILOBA_SCREENSHOTS_DIR, BILOBA_INLINE_SCREENSHOTS, BILOBA_INTERACTIVE) and BilobaConfig knobs; guidance on interpreting Outline() and A11yOutline().

Quick Start

Run Biloba with a failing spec to generate DOM outlines and failure artifacts for debugging.

Frequently Asked Questions about debug-failures

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

FAQPage Schema
How do I debug Biloba spec failures using DOM outlines and screenshots?

Biloba spec failure debugging uses on-failure artifacts like DOM outlines and screenshots. Enable these artifacts to inspect mismatch points and quickly diagnose why a browser spec failed during test runs.

How do I configure Biloba to save failure screenshots in a CI pipeline?

Configure failure screenshots in CI pipelines by setting the BILOBA_SCREENSHOTS_DIR environment variable. Biloba detects the CI environment and saves failure artifacts to the specified directory for automated test pipeline analysis.

Does Biloba test output work with AI agents like Claude Code or Cursor?

Biloba adapts failure output for AI agents like Claude Code and Cursor. Environment variables such as BILOBA_INLINE_SCREENSHOTS format DOM outlines and failure artifacts so AI-assisted tooling can interpret and resolve spec failures.

What environment variables control Biloba interactive debugging output?

Biloba interactive debugging is controlled by the BILOBA_INTERACTIVE, BILOBA_SCREENSHOTS_DIR, and BILOBA_INLINE_SCREENSHOTS environment variables. These settings adjust how failure artifacts and DOM outlines render for human developers versus CI pipelines.

What is the difference between b.Outline() and b.A11yOutline() for failure analysis?

b.Outline() generates a standard DOM outline while b.A11yOutline() generates an accessibility-focused DOM outline. Both surface on-failure artifacts to help identify mismatch points during browser spec debugging in Biloba.

When should I use BilobaConfig knobs instead of environment variables for test artifacts?

Use BilobaConfig knobs instead of environment variables when you need persistent, programmatic control over test artifacts within spec code. Environment variables like BILOBA_SCREENSHOTS_DIR are better for per-run CI pipeline configurations.