TestPrune.Falco 2.0.3

TestPrune.Falco

When you change a route handler, only re-run the integration tests that hit that route.

This is an extension for TestPrune that connects Falco URL routes to integration tests. If you change the handler for /api/users/{id}, it finds the tests that make requests to that URL and runs just those.

Status: early alpha. This is a young project, substantially AI-written, and still finding its shape. Behavior and APIs shift between versions, so pin a version and expect surprises.

Installation

dotnet add package TestPrune.Falco

How to use it

1. Store your route mappings during indexing

Tell TestPrune which source files handle which URLs. Each entry is a RouteHandlerEntry; db.RebuildRouteHandlers clears and rewrites the whole route table:

open TestPrune.AstAnalyzer // RouteHandlerEntry

db.RebuildRouteHandlers [
    { UrlPattern = "/api/users/{id}"
      HttpMethod = "GET"
      HandlerSourceFile = "src/Web/Handlers/Users.fs" }
    { UrlPattern = "/api/users/{id}"
      HttpMethod = "PUT"
      HandlerSourceFile = "src/Web/Handlers/Users.fs" }
]

2. Create the extension and query affected tests

The extension reads routes through a RouteStore — build one from your Database with toRouteStore:

open TestPrune.Ports        // toRouteStore, toSymbolStore
open TestPrune.Extensions   // ITestPruneExtension, AffectedTest

let extension =
    FalcoRouteExtension(
        integrationTestProject = "MyApp.IntegrationTests",
        integrationTestDir = "tests/MyApp.IntegrationTests",
        routeStore = toRouteStore db
    )

// Affected test classes, directly:
let affected = extension.FindAffectedTestClasses(changedFiles, repoRoot)
// -> [{ TestProject = "MyApp.IntegrationTests"; TestClass = "UsersTests" }]

To feed those couplings into TestPrune's dependency graph instead, use the ITestPruneExtension interface, which returns edges to inject:

let edges =
    (extension :> ITestPruneExtension)
        .AnalyzeEdges (toSymbolStore db) changedFiles repoRoot
// -> Dependency list (test symbol -> handler symbol, kind SharedState)

How it works

1. Checks if any changed file is a known handler (from the route table)
2. Looks up which URL patterns that handler serves
3. Scans your integration test .fs files for those URLs (/api/users/{id} matches /api/users/123 in your test code)
4. Returns the test classes from files that reference affected routes (FindAffectedTestClasses), or those couplings as graph edges (AnalyzeEdges)

Documentation

• Full documentation
• API reference