[image: with-go-test-with-test-runner.png] We implemented a basic test impact analysis that identifies and then executes affected tests for a change, e.g. for a range of commits. Our benchmark for the repositories we looked at shows an average 29% reduction in test execution time. I am very much looking forward to hearing how your repositories perform!
Details of the benchmark and how the analysis/command works can be found here: https://symflower.com/en/company/blog/2024/test-impact-analysis/. The approach right now is to query a diff using Git and then check which Go packages are affected. In the next iterations, we will bring this analysis down to individual function and test-case level. The eventual goal is to use our symbolic execution engine to allow for even deeper granularity. At one point i like to have it as a drop-in command for `go` but right now execution looks like this (for all changes of the last commit to now): ``` symflower test-runner --commit-from HEAD~ -- go test -v ``` Looking forward to your feedback! Cheers, Markus -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/0d4cf273-ad2f-4b51-ba9d-d18081535700n%40googlegroups.com.
