# Redamon Testing

How RedAmon tests actually run and how to author them: the per-file Docker gate, the...

- Repository: https://github.com/samugit83/redamon (3261 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add samugit83/redamon --skill redamon-testing -g -a claude-code -y`
Codex: `npx skills add samugit83/redamon --skill redamon-testing -g -a codex -y`
Cursor: `npx skills add samugit83/redamon --skill redamon-testing -g -a cursor -y`
Gemini CLI: `npx skills add samugit83/redamon --skill redamon-testing -g -a gemini-cli -y`

## Description

How RedAmon tests actually run and how to author them: the per-file Docker gate, the unit/integration/live tiers, and the failure modes that make a green run a lie. Trigger: editing any test_*.py, *.test.ts(x) or tests/*.sh; a test that is red, skipped or xfailed; a request to "run the tests", "make it green" or check coverage; editing redamon.sh cmd_test, tooling/scripts/pytest_isolated.py, any conftest.py or any pytest.ini.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## When to Use

- Writing or fixing a test anywhere in the repo, or deciding where a new test goes.
- A test is red/skipped/xfailed and you must decide whether it is real.
- You were asked to run the suite or verify a change "works".

The repo-wide rule "never validate with host `pytest`, use the Docker gate" lives
in the root [AGENTS.md](../../AGENTS.md) CRITICAL RULES; this skill is everything
*after* that: isolation, tiers, and how to write a test that asserts something.

---

## Critical Rules

The rest: https://github.com/samugit83/redamon/blob/HEAD/skills/redamon-testing/SKILL.md