testing

name	testing
description	Execute Python-based validation and regression test suites for the 3D Printer Slicer API (Prusa/Orca). Use this when asked to run tests, verify endpoint behavior, check queue concurrency, or validate pricing lifecycles.

Use this skill whenever API endpoints, slicing logic, pricing, or queue concurrency needs to be tested.

Slash entrypoint:

• Use /testing to run the repository test workflow and summarize markdown report evidence.

Full agent definitions with scope, responsibilities, hard rules, and scope boundaries are mirrored in .github/agents/test-engineer.md and .claude/agents/test-engineer.md. Read that file for complete context when writing new tests or extending existing ones.

Quick Command Reference

1. Full suite wrapper

   • Command: python tests/testing-scripts/slicing/full_api_test_runner.py
   • Report: tests/testing-scripts/results/full_api_test_result.md

2. Engine-specific matrix runners

   • Orca FDM: python tests/testing-scripts/slicing/full_api_orca_fdm_test_runner.py
   • Prusa FDM: python tests/testing-scripts/slicing/full_api_prusa_fdm_test_runner.py
   • Prusa SLA: python tests/testing-scripts/slicing/full_api_prusa_sl1_test_runner.py

3. Isolated feature tests

   • Unsupported upload rejection: python tests/testing-scripts/slicing/unsupported_upload_test_runner.py
   • Pricing lifecycle: python tests/testing-scripts/pricing/pricing_cycle_test_runner.py
   • Admin output listing: python tests/testing-scripts/admin/admin_output_files_test_runner.py
   • Rate-limit regression: python tests/testing-scripts/rate_limit/rate_limit_regression_test_runner.py

4. Queue and concurrency test

   • Command: python tests/testing-scripts/queue/queue_concurrency_test_runner.py --count <N> --retry-on-429 3

Execution Workflow

1. Identify which subsystem must be validated.
2. Run the exact matching test script.
3. Wait for completion.
4. Immediately read the generated report in tests/testing-scripts/results/.
5. Summarize pass/fail details and notable findings.

Troubleshooting

• If admin tests fail with 401/403, verify ADMIN_API_KEY in .env matches the running server.
• If slice tests fail with connection errors, verify API health endpoint before rerun.
• If a slice matrix row returns non-2xx but is marked successful, verify the report's Expected, Status, and ErrorCode columns match an explicitly declared fail-fast outcome.

Validation Checklist

• Chosen runner matches requested behavior scope.
• Corresponding markdown report was read after execution.
• Summary includes failures, retries, and key diagnostics.