test/failing-test

Execute a Node tool that intentionally fails to expose stdout and stderr.

Updated Dec 30, 2025

Search Tags:#automation #testing #node

Ready to run

npx skills add https://github.com/while-basic/enact-template --skill test-failing-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test/failing-test
Source: https://github.com/while-basic/enact-template/tree/main/test-tools/failing-test
Command: npx skills add https://github.com/while-basic/enact-template --skill test-failing-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers observe and validate error visibility by executing a small Node.js tool that intentionally fails, exposing stdout, stderr, and error messages for debugging and logging workflows.

Core Features & Use Cases

Deterministic failure sequence: runs script.js which prints messages to stdout and stderr before exiting with a non-zero code for testing error visibility.
Observability validation: demonstrates how logs capture errors, stack traces, and console output in CI and local runs.
Use Case: verify that a tool runner properly surfaces failures to dashboards and alerting systems when a tool crashes.

Quick Start

Run the failing tool to trigger an error and observe the stdout and stderr outputs prior to termination.

Frequently Asked Questions about test/failing-test

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

FAQPage Schema

How do I test error visibility when a Node.js script fails?▼

Testing error visibility involves running a Node.js script that intentionally fails. This process exposes stdout, stderr, and error messages, allowing you to validate how failures are captured by logging workflows.

How do I verify my CI pipeline correctly captures stdout and stderr on failure?▼

Verifying CI pipeline error capture requires triggering a deterministic failure sequence. Running a script that prints messages to stdout and stderr before exiting with a non-zero code validates that dashboards and alerting systems properly surface crashes.

Does testing error visibility require a Node.js runtime?▼

Yes, testing error visibility with this approach requires a Node.js runtime. It executes a script.js file that handles the deterministic failure sequence and outputs console messages prior to termination.

What is the best way to validate logging workflows for tool crashes?▼

The best way to validate logging workflows for tool crashes is to use an observability validation tool. It intentionally triggers errors and stack traces, demonstrating how logs capture failures across both local runs and CI environments.

Why are my error messages not surfacing in dashboards when a tool crashes?▼

Error messages may not surface in dashboards if the tool runner lacks proper observability validation. Running an intentional failure tests whether stdout, stderr, and non-zero exit codes are correctly captured by alerting systems.

When do I need to validate error visibility in testing environments?▼

You need to validate error visibility in testing environments when integrating debugging and logging workflows. It ensures that stack traces, console output, and non-zero exit codes are fully exposed during both local runs and CI execution.