debugging-failed-tests

Fetch failed test details and backtraces from Buildkite Test Engine.

Updated Aug 27, 2026

Search Tags:#testing #ci/cd #debugging #test failures #buildkite #test engine

Ready to run

npx skills add https://github.com/blaknite/agent-skills --skill debugging-failed-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging-failed-tests
Source: https://github.com/blaknite/agent-skills/tree/main/debugging-failed-tests
Command: npx skills add https://github.com/blaknite/agent-skills --skill debugging-failed-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers quickly identify and diagnose the root cause of failed automated tests in their CI/CD pipeline, reducing debugging time and improving code quality.

Core Features & Use Cases

Identify Failing Tests: Pinpoint specific tests that failed within a Buildkite Test Engine run.
Retrieve Backtraces & Errors: Fetch detailed error messages and stack traces for failed tests.
Analyze Test Results: Examine test execution details to understand failure patterns and environmental factors.
Use Case: When a Buildkite pipeline reports test failures, use this Skill to get a list of the failed tests, their error messages, and relevant code locations to start fixing them.

Quick Start

Use the debugging-failed-tests skill to find the failed tests for Buildkite suite 'my-org/my-suite' in run 'run-id-123'.

Frequently Asked Questions about debugging-failed-tests

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

FAQPage Schema

How do I debug failed tests in a Buildkite CI/CD pipeline?▼

To debug failed tests in a Buildkite CI/CD pipeline, you can retrieve execution details directly from the Buildkite Test Engine to pinpoint specific test names, failure reasons, and expanded backtraces for diagnosis.

What buildkite test engine data do I need to retrieve test failure backtraces?▼

Retrieving test failure backtraces requires a valid Buildkite API token for authentication, along with the specific test suite identifier and the unique test run ID to fetch detailed error messages and stack traces.

Why does my Buildkite test suite report failures, and how can I identify the root cause?▼

Buildkite test suite failures can be diagnosed by fetching execution details to analyze failure patterns, environmental factors, and relevant code locations, helping you quickly identify the root cause of the broken tests.

Can I get a list of specific failed tests from a Buildkite test run?▼

Yes, you can get a list of specific failed tests from a Buildkite test run by querying the Test Engine with your suite name and run ID to pinpoint exactly which tests failed within the execution.

What's the best way to analyze test execution details for CI/CD test failures?▼

The best way to analyze test execution details for CI/CD test failures is to fetch expanded backtraces and error messages from the Test Engine, enabling you to examine environmental factors and understand failure patterns.