gateway-eunit

Run Yuzu gateway eunit tests with rebar3 and --dir discovery.

15|7|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Tr3kkR/Yuzu --skill gateway-eunit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gateway-eunit
Source: https://github.com/Tr3kkR/Yuzu/tree/main/.claude/skills/gateway-eunit
Command: npx skills add https://github.com/Tr3kkR/Yuzu --skill gateway-eunit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exposes a reliable, guided workflow for running the Yuzu gateway Erlang eunit test suite, including environment setup, deterministic test discovery, and clear output interpretation.

Core Features & Use Cases

  • Source and prepare the Erlang toolchain, enable deterministic test discovery with --dir, and run the gateway eunit tests.
  • Provide actionable guidance to verify gateway changes, chase eunit flakes, and interpret failing or flaky results.
  • Ensure consistent results across runs by documenting required commands and expected outputs.

Quick Start

From the repo root, source the Erlang toolchain, then navigate to the gateway directory and run rebar3 eunit --dir apps/yuzu_gw/test.

Frequently Asked Questions about gateway-eunit

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

FAQPage Schema
How do I run Erlang eunit tests reliably for my gateway component?

Source the Erlang toolchain, navigate to the gateway directory, and execute rebar3 eunit --dir apps/yuzu_gw/test using the --dir workaround for deterministic test discovery and consistent results.

Why does rebar3 eunit fail to discover my Erlang test files?

Standard rebar3 eunit test discovery can fail in certain directory structures. Using the --dir workaround explicitly targets the test folder, ensuring reliable detection of your eunit test suite.

What do I need to interpret flaky eunit test results for my gateway changes?

Interpreting flaky eunit test results requires explicit guidance on expected outputs. This workflow provides actionable steps to chase eunit flakes and verify outcomes when validating your gateway component.

Do I need rebar3 to automate Erlang eunit testing for the Yuzu gateway?

Yes, rebar3 and the Erlang toolchain are required to automate eunit testing for the Yuzu gateway. Sourcing the environment and using rebar3 with the --dir flag ensures your test suite runs consistently.

What is the best way to validate gateway changes without encountering eunit flakes?

The best way to validate gateway changes is to use a guided eunit workflow applying the --dir workaround for deterministic test discovery, ensuring consistent results and clear output interpretation across runs.