Skip to content
Back to skills

Test:Review

ASecurity

Review tests for quality - assertive checks, no hidden skips, proper coverage

  • 299 stars
  • 0 votes
  • 1 copy
  • 9 views
  • Added September 20, 2026
testingbash

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add rossoctl/rossoctl --skill test:review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Test:Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Test:Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rossoctl-test-review/badge)](https://www.skillsdirectory.com/skills/rossoctl-test-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: test:review
description: Review tests for quality - assertive checks, no hidden skips, proper coverage
---

# Test Review

Review test quality to ensure tests actually catch failures.

## When to Use

- After writing new tests (before committing)
- When reviewing a PR with test changes
- When tests pass but behavior seems wrong
- Periodic test suite health check

## Anti-Patterns to Catch

| Anti-Pattern | Problem | Fix |
|-------------|---------|-----|
| `assert True` | Always passes, tests nothing | Assert specific values |
| `@pytest.mark.skip` without reason | Hides failures silently | Add reason or remove |
| `@pytest.mark.xfail` without ticket | Accepted failures without tracking | Link to issue |
| `try/except: pass` in test | Swallows errors | Let exceptions propagate |
| `assert response is not None` | Only checks existence, not correctness | Assert status code + content |
| `assert len(items) > 0` | Doesn't verify content | Assert specific items or properties |
| Empty test body | Test exists but does nothing | Implement or delete |
| Hardcoded timeouts `sleep(30)` | Flaky, slow | Use `wait_for` / retry pattern |

## Review Checklist

- [ ] **Assertive**: Every test asserts specific expected values
- [ ] **No silent skips**: `@skip` has a reason and linked issue
- [ ] **No xfail without tracking**: `@xfail` references a ticket
- [ ] **Error cases tested**: Not just happy path
- [ ] **Deterministic**: No flaky timing dependencies
- [ ] **Isolated**: Tests don't depend on execution order
- [ ] **Named clearly**: Test name describes what it verifies
- [ ] **Cleanup**: Resources created in test are cleaned up

## Review Command

Search for anti-patterns in test files:

```bash
grep -rn "assert True\|assert False\|@pytest.mark.skip\|@pytest.mark.xfail\|pass$" rossoctl/tests/
```

Search for weak assertions:

```bash
grep -rn "is not None\|!= None\|assert .*>" rossoctl/tests/ | grep -v "# ok"
```

## Related Skills

- `test:write` - Write new tests following standards
- `test:run-kind` - Run tests on Kind
- `test:run-hypershift` - Run tests on HyperShift
- `tdd:ci` - TDD workflow that includes test review

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.