Phase 5: Affected tests discovery — auto-identify test files impacted by changes #460

Activity

1. ajianaz

   added this to the v0.13.0 — Code Intel Enhancements milestone on Aug 3, 2026
2. ajianaz

   added

   enhancementNew feature or requestNew feature or request

   priority:low

   scope:coreCore review engineCore review engine

   scope:code-intelCode intelligence — indexing, graph, impact analysisCode intelligence — indexing, graph, impact analysis

   phase-3Phase 3: ArchitecturePhase 3: Architecture

   and removed

   phase-3Phase 3: ArchitecturePhase 3: Architecture

   on Aug 3, 2026
3. ajianaz commented on Aug 3, 2026

   

   ajianaz

   on Aug 3, 2026

   CollaboratorAuthor

   More actions

   Implemented in PR #461 (merged to develop).

   What was delivered:

   • Affected tests discovery in build_brain_context() (review.rs) — walks impact graph, collects files containing 'test' or 'spec'
   • Affected tests discovery in build_scan_context() — same logic for scan mode
   • MCP tool cora.find_affected_tests — takes file list, returns affected test files via 2 strategies:
     1. Call graph traversal: find callers in test files
     2. Naming convention: batch LIKE query for test/spec file patterns

   Both strategies combined and deduplicated.
4. ajianaz

   closed this as completedon Aug 3, 2026