# Run Tests

> Run dojo tests, analyze failures, and debug issues. Use when testing code changes, running pytest, verifying fixes, or debugging test failures. Use when this capability is needed.

- Skill: `tomevault-io/run-tests` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/run-tests`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/run-tests/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/run-tests

---


# Running Tests

Tests take ~10 minutes to run, so run them as a background process.

## Running All Tests

Start tests in background:
```bash
./deploy.sh -b -t 2>&1 | tee /tmp/test.log &
```

Monitor progress:
```bash
tail -f /tmp/test.log
```

## Running Specific Tests

To run only specific test files quickly, edit `deploy.sh` line:
```bash
test_container pytest --order-dependencies --timeout=60 -v . "$@"
```

Change it to run a specific file:
```bash
test_container pytest --order-dependencies --timeout=60 -v test_belts.py "$@"
```

Then run:
```bash
./deploy.sh -b -t 2>&1 | tee /tmp/test.log &
```

**Important:** After specific tests pass, restore the original line and rerun ALL tests.

## Analyzing Failures

After tests complete, analyze `/tmp/test.log`:
1. Search for `FAILED` to find failing tests
2. Search for `ERROR` to find errors
3. Look at the full traceback for each failure

## Debugging Workflow

1. **Identify failures** - Analyze `/tmp/test.log` for FAILED/ERROR
2. **Find root cause** - Look at tracebacks, check CTFd logs with:
   ```bash
   docker exec $(basename "$PWD") docker logs ctfd 2>&1 | tail -100
   ```
   You can also look at all any of the containers inside of `docker exec $(basename "$PWD")`, the whole list including names is in docker-compose.yml.
3. **If root cause unclear** - Add logging to help understand, then rerun tests
4. **Fix the root cause** - Don't just fix symptoms
5. **Run specific tests** - Edit deploy.sh to run just the affected test file
6. **Verify fix** - Ensure the specific test passes
7. **Run ALL tests** - Restore deploy.sh and run full suite before declaring success

## Key Commands

```bash
# Start all tests (background)
./deploy.sh -b -t 2>&1 | tee /tmp/test.log &

# Check if tests are still running
jobs

# View test output
cat /tmp/test.log

# Search for failures
grep -E "(FAILED|ERROR|error)" /tmp/test.log

# View CTFd logs for debugging
docker exec $(basename "$PWD") docker logs ctfd 2>&1 | tail -200

# Run DB queries for debugging
docker exec -i $(basename "$PWD") dojo db
```

## Multinode Testing

After all singlenode tests pass, run multinode tests to verify the full cluster setup:

```bash
./deploy.sh -b -M -t 2>&1 | tee /tmp/test-multinode.log &
```

Monitor progress:
```bash
tail -f /tmp/test-multinode.log
```

Multinode mode starts 3 containers (1 main + 2 workspace nodes) and tests the distributed architecture. Some things that only run on the main node (like stats-worker) need special handling in multinode.

## Critical Reminder

**ALWAYS rerun all singlenode tests before declaring everything passed.** Fixing one test can break others.

**After singlenode tests pass, run multinode tests (`-M` flag) to verify the full cluster setup works correctly.**

---
> Source: [pwncollege/dojo](https://github.com/pwncollege/dojo) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-18 -->