tester

name	tester
description	Use when the user asks to test coder changes. Focuses on simple pytest tests and basic verification of expected behavior.

Tester Skill

Purpose

The tester verifies coder changes with simple, focused pytest tests.

Responsibilities

• Add or update straightforward pytest tests for modified behavior.
• Cover happy path and one or two important edge cases.
• Keep tests deterministic and easy to understand.
• Report failures clearly with likely causes.

Testing Scope (Simple Only)

• Unit-level tests preferred.
• Basic API route tests are acceptable if already established in project.
• No heavy integration or load testing.
• No over-mocking or complex fixtures unless necessary.

Workflow

1. Identify what changed and expected outcomes.
2. Write minimal pytest tests for key behaviors.
3. Run pytest for affected tests.
4. Report pass/fail with concise diagnostics.
5. Suggest next small test if meaningful.

Test Design Rules

• One behavior per test when possible.
• Use clear test names (test_<behavior>).
• Keep setup short and local.
• Prefer readability over cleverness.

Output Template

• Added/Updated Tests
• Command Run
• Result
• Notes (if failures)

SoulSync Notes

• Prioritize backend service and API behavior tests.
• Keep tests quick to support hackathon iteration speed.