🎺 FAAAAH on Fail

Because test failures should be dramatic.

FAAAAH on Fail plays the popular FAAAA sound whenever your tests fail.

Features

• 🌍 Multi-framework support — Jest, Vitest, pytest, RSpec, Flutter, Go, Rust, JUnit, PHPUnit, and 20+ more
• 🎺 Multiple built-in sounds — FAAAAH, Fatality, Joker, or random
• 🔊 Custom sounds — swap the defaults with your own .wav file
• 🎚️ Volume control — from subtle shame to full office broadcast
• 💬 Random failure messages — comedic commentary to soften the blow
• 🖥️ Cross-platform — macOS, Windows, and Linux
• ⚙️ Extensible — add your own test commands via settings

How It Works

FAAAAH on Fail listens for test failures using two detection layers:

1. Shell Integration — monitors terminal commands. When a recognized test command (npm test, pytest, cargo test, etc.) exits with a non-zero code, FAAAAH fires.
2. Task Exit Codes — listens for VS Code tasks in the Test group or matching test command patterns.

Note: Tests run exclusively through VS Code's Test Results panel without spawning a terminal may not be detected yet. This is a VS Code API limitation — the test observation API is not yet stable. Most test extensions spawn terminals under the hood, so coverage is broad in practice.

Supported Frameworks

Works out of the box with any test runner that executes in a terminal or task:

Jest | Vitest | Mocha | Jasmine | Karma | Ava | Cypress | Bun | Deno | pytest | tox | nox | RSpec | ExUnit | Flutter | Dart | Go | Rust | JUnit | Gradle | Maven | PHPUnit | dotnet test | CTest | Maestro | and more...

Don't see yours? Add it:

{
  "faaaahOnFail.extraTestCommands": ["my-custom-runner"]
}

Installation

Search for "FAAAAH on Fail" in the VS Code Extensions panel, or:

ext install Mastersam.faaaah-on-fail

Commands

Settings

Custom Sounds

{
  "faaaahOnFail.customSoundPath": "/path/to/your/sad-sound.wav"
}

License

MIT