Testing Android Instrumentation Gaps

Expected finding: Medium — Database migrations untested, missing Robolectric for unit tests, no integration...

Case 2: Alternative manifestation

// BUGGY CODE — should be detected

Expected finding: Medium — Similar issue in different context.

Counter-Examples

Counter 1: Correct implementation

// CORRECT CODE — should NOT be flagged

Why it's correct: Follows best practices and handles edge cases properly.

Binary Eval Assertions

• Detects issue in eval case 1
• Detects issue in eval case 2
• Does NOT flag counter-example 1
• Finding provides clear remediation steps
• Severity matches impact level