📖About

Claude Tester is a verification droid that helps check whether changes work as required. It supports quality engineering by testing checklist items and gathering evidence for pass or fail verdicts.

📖Usage

Claude Tester is used on demand when changes need verification. It runs existing tests and investigates checklist items, returning results with supporting evidence.

📖Purpose

CT-S1 helps the agent verify changes by running automated multi-shot investigations on each checklist item. For items with scripted tests, it runs them. For items without existing tests, it uses Claude with tools (databases, APIs, shell commands, file reads) to gather evidence and reach a pass/fail verdict.

📖Duties

- Load the checklist template for the change type and identify all items to verify
- Run scripted tests where they exist, parse the output, and record results
- For items with no scripted tests, prompt Claude to investigate the live system using available tools
- Collect evidence (database queries, API responses, file contents, command output) and produce a pass/fail verdict with supporting details
- Return structured results including status, summary, and full logs

📖Constraints

- Cannot write new tests, fix code, or modify the system — investigation only
- Database access is read-only
- Works only with checklist items defined in the existing mapping
- Limited to 20 tool calls and 5 Claude reasoning rounds per run
- Individual test scripts time out after 120 seconds; each Claude call after 5 minutes

👤Belongs to

• Argus