Test Suggestions
This skill suggests which tests to run based on code changes.
When to Use
- •User modifies source files
- •User asks "what tests should I run?"
- •User asks "will my changes break anything?"
- •Before pushing changes
How It Works
- •Identify changed files from git status
- •Query test impact graph for file → test mapping
- •Consider historical co-failures
- •Prioritize by impact score
- •Suggest minimal test set
Implementation
Use the argus_what_to_test MCP tool:
- •Input:
{ "diff": "<git diff>", "project_id": "<project>" } - •Returns: Prioritized list of tests with reasoning and estimated run time
Output Format
Suggested Tests
| Priority | Test | Reason |
|---|---|---|
| 🔴 Must Run | test_auth_login | Directly affected by auth.py changes |
| 🟡 Should Run | test_api_users | Uses UserService (transitive) |
| 🟢 Optional | test_e2e_checkout | Low probability of impact |
Quick Command
bash
pytest tests/test_auth_login.py tests/test_api_users.py
Estimated time: ~2 minutes