test-selection

Performs Bazel Target Diffing between two revisions in Git, allowing for Test Target Selection and Selective Building

🚗💻 SDC Tool Competition

Ekstazi is a Regression Test Selection algorithm. This is a Pytest plugin implementing it.

Modern dependency-based test selection for Maven, Gradle & JUnit 5

Map your test terrain — understand, optimize, and protect your test system with structural intelligence. AI and regular test parity for CI.

Run only the tests affected by your changes. Selective test execution inspired by Stripe.

Gradle plugin to run tests with ekstazi - the lightweight test selection library

Selects only the tests affected by your code changes by mapping per-test runtime coverage against Git diffs, cutting regression suite execution time.

Cut your test time to the minimum. Function-level test impact analysis via static AST for TypeScript, Go, and Rust.

A Static Class-level Regression Test Selection Tool

Code for "A Multi-Objective Test Selection Tool using Test Suite Diagnosability"

Impact-analysis and test selection CLI for OpenHarmony ArkUI workspaces. Automates XTS target resolution for changed files.

More precise regression test selection via reasoning about semantics-modifying changes

Skip tests that don't matter. This Maven plugin uses bytecode instrumentation to track which tests cover which classes, then uses Git to run only the tests impacted by your changes.

Run only the tests affected by your changes — intelligent test selection plugin for Vitest

Agent triage, measured: does this edit need a human, or can the AI handle it? We measure whether the graph under the agent can reach the tests that guard a change (0.42 pooled, 7 repos) and ship the fail-closed gate that routes unproven maps to human verification. CLI · MCP · SARIF · in-engine on HydraDB.

Test intelligence for Go — test impact analysis, line-level test selection, mutation testing, flaky-test detection, and coverage risk mapping in one static binary.

Instead of running the whole suite on every PR, analyze the diff's dependency graph and propose the minimal set of tests actually at risk — with an LLM fallback for dynamic-import edge cases the static graph can't resolve.

GitHub Action: run only the Playwright specs a PR can affect. Reads @Covers declarations from spec headers, and escalates to the full suite whenever narrowing can't be justified.

Trace an API route through the code that serves it, overlay the test evidence that covers it, and turn a diff into the specs that must run.