exp-assertion-quality

# Assertion Diversity Analysis Analyze .NET test code to measure how varied and meaningful the assertions are. Produce a metrics report that reveals whether tests verify different facets of correctness — not just "output equals X" but also structure, exceptions, state transitions, side effects, and invariants. ## Why Assertion Diversity Matters Low assertion diversity signals shallow testing. Tests may pass while bugs hide in unasserted logic. Common symptoms: | Problem | Symptom | Consequence | |---------|---------|-------------| | Trivial assertions | `Assert.IsNotNull(result)` only | Test passes but doesn't verify correctness | | Single-value obsession | Always check one field or return value | Bugs in unasserted logic slip through | | No negative assertions | Never check what shouldn't happen | Regressions sneak in through false positives | | No state checks | Don't verify object state changes | Missed side-effects or lifecycle issues | | No structural checks | Only assert top-level value | Bugs in nested objects go unnoticed | | Assertion-free tests | Tests that call but don't verify | Code coverage lies; false security | ## When to Use - User asks to evaluate assertion quality or depth - User asks "are my tests actually testing anything meaningful?" - User wants to know if test assertions are too shallow or trivial - User asks for assertion coverage metrics or diversity analysis - User suspects tests give false confidence despite passing ## When Not to Use - Use...