This is something I've asked for the best part of a decade and one of the causes is the disconnect between test and development.

So to solve this I've been developing `ccc`, a static analyser & runtime instrumentation tool to determine: [for any given change; what is the minimum required test to cover that change].

Preliminary benchmarks and testing for a multi-component SaaS with a Python Test suite (integration, perf etc) have shown positive results. Test suites requiring full-workflow runs (100s of tests) reduced to single or a handful of smaller faster tests.

Looking for feedback and to hear if anyone working on large code-bases experiences similar problems in their projects.

Cheers!