Files
security-game/tools/tests/README.md
T
zwitschi e4e1566e55
Full build / Import + headless tests (push) Successful in 38s
Full build / Full desktop build + optional release (push) Skipped
Organize tools and move Python tests into tools/tests
2026-11-03 19:45:00 +01:00

26 lines
789 B
Markdown

# Python Tooling Tests
Unit tests for the scripts in `tools/`. They use the standard library
`unittest` plus Pillow; no Godot or Blender process is started.
Run them from the repository root:
```bash
python3 -m pip install -r requirements-tools.txt
python3 -m unittest discover -s tools/tests -t tools -p 'test_*.py'
```
The `-t tools` top-level directory is required: the tests import the tool
modules by their plain names (for example `import blender_assets`).
Individual example:
```bash
python3 -m unittest tools.tests.test_model_review -v
```
(Module-style invocation requires `tools/tests/__init__.py`, which is committed.)
These tests do not call OpenRouter. The judge/image tests mock the HTTP layer;
live generation and judging remain manual, development-only operations.