56 lines
1.2 KiB
YAML
56 lines
1.2 KiB
YAML
name: test-writer
|
|
description: >
|
|
Adds test coverage for untested modules. Finds coverage gaps,
|
|
writes meaningful tests, verifies they pass.
|
|
|
|
model:
|
|
preferred: qwen3:30b
|
|
fallback: claude-sonnet-4-20250514
|
|
max_turns: 30
|
|
temperature: 0.3
|
|
|
|
tools:
|
|
- terminal
|
|
- file
|
|
- search_files
|
|
- patch
|
|
|
|
trigger:
|
|
issue_label: tests
|
|
manual: true
|
|
|
|
repos:
|
|
- Timmy_Foundation/the-nexus
|
|
- Timmy_Foundation/hermes-agent
|
|
|
|
steps:
|
|
- read_issue
|
|
- clone_repo
|
|
- create_branch
|
|
- dispatch_agent
|
|
- run_tests
|
|
- create_pr
|
|
- comment_on_issue
|
|
|
|
output: pull_request
|
|
timeout_minutes: 15
|
|
|
|
system_prompt: |
|
|
You are a test engineer for the {{repo}} project.
|
|
|
|
YOUR ISSUE: #{{issue_number}} — {{issue_title}}
|
|
|
|
RULES:
|
|
- Write tests that test behavior, not implementation details.
|
|
- Use tox -e unit to run tests. Never run pytest directly.
|
|
- Tests must be deterministic. No flaky tests.
|
|
- Conventional commits: test: <description> (#{{issue_number}})
|
|
- If the module is hard to test, file an issue explaining why.
|
|
|
|
WORKFLOW:
|
|
1. Read the issue for target module paths
|
|
2. Read the existing code to understand behavior
|
|
3. Write focused unit tests
|
|
4. Run tox -e unit — all tests must pass
|
|
5. Commit, push, create PR
|