testing-dags

Trigger Airflow DAG runs and wait for completion to determine success or failure.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/miptah21/skills --skill testing-dags-miptah21
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-dags
Source: https://github.com/miptah21/skills/tree/main/.agents/skills/testing-dags
Command: npx skills add https://github.com/miptah21/skills --skill testing-dags-miptah21

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Testing Airflow DAGs often fails late and wastes time on slow, manual troubleshooting; this skill helps you run a DAG, capture the failure context, and iteratively fix issues until the pipeline succeeds.

Core Features & Use Cases

  • Trigger-and-wait validation: Run a DAG run and wait for completion to quickly determine success vs failure.
  • Targeted failure debugging: Retrieve run diagnostics and task logs for failed tasks, including retry attempts.
  • Iterative fix-and-retest loop: Apply a fix and rerun using the same minimal workflow to converge on a working DAG.

Use case example: You deploy changes to a dbt/SQL-based Airflow DAG and it fails on a specific task; trigger the DAG, inspect logs for the failed task instance, apply the fix, and retest.

Quick Start

Ask the agent to test the DAG end-to-end by triggering and waiting for its completion using the Airflow entrypoint command, then debug only if it fails.

Frequently Asked Questions about testing-dags

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

FAQPage Schema
How do I trigger an Airflow DAG and wait for it to complete?

To trigger an Airflow DAG and wait for completion, use the `af runs trigger-wait` command to start a DAG run and monitor it until it finishes, returning a success or failure state for validation.

How do I debug a failed Airflow DAG task using run diagnostics?

Debug a failed Airflow DAG task by running `af runs diagnose` to retrieve run diagnostics, then use `af tasks logs` to inspect the specific task instance logs and identify the root cause of the pipeline failure.

What is the best way to run an iterative fix-and-retest loop for Airflow pipelines?

The best way to run an iterative fix-and-retest loop for Airflow pipelines is to trigger the DAG, inspect task logs on failure, apply a fix, and rerun the same minimal workflow repeatedly until the multi-step pipeline succeeds.

Can I retrieve retry attempt logs for failed tasks in Airflow?

Yes, you can retrieve retry attempt logs for failed tasks in Airflow by using the targeted failure debugging workflow, which captures run diagnostics and extracts specific task instance logs including retry attempts.

Why does testing multi-step Airflow pipelines fail late and how do I diagnose it?

Testing multi-step Airflow pipelines fails late due to slow manual troubleshooting; diagnose it by triggering a DAG run, waiting for completion, and extracting run diagnostics and task logs to pinpoint the exact failure context.