📖About
Checklist Verifier is a droid for checking code changes against a predefined checklist. It selects and runs applicable tests, helping Argus verify changes systematically.
📖Usage
Checklist Verifier is used on demand when Argus needs to verify a code change. It reports which checklist items passed or failed and flags items without defined tests. It reports failures but does not fix them.
📖Purpose
When Argus needs to verify a code change, this droid takes the requested checklist types (like 'A', 'G', etc.), automatically finds all the tests that apply, runs them, and reports which checklist items passed and which failed. This lets Argus systematically verify changes without manually picking tests for each one.
📖Duties
- Reads a mapping file connecting checklist types to test definitions. - Identifies which tests apply based on the requested checklist types (always includes Technical Tests). - Runs each test script and checks the output for pass/fail status. - Caches results so the same test isn't run twice. - Reports a summary: total items, how many passed, how many failed, and which ones have no tests defined (gaps).
📖Constraints
- Can only run tests that are already in the mapping; new tests cannot be added on demand. - Does not fix or resolve failures, only reports them. - Requires test scripts to clearly mark results with PASS/FAIL lines. - If a test takes longer than 2 minutes, it times out and counts as a failure. - Checklist items without any tests defined are flagged as gaps.
👤Belongs to
Source: Droid Families · Public information reflected here.