Test Impact Explorer

Source on GitHub

Paste a diff and see exactly which tests need to run. Every selected test comes with the import chain that connects it to your change, so you can check the reasoning instead of trusting it.

1. Project

sample-shop

19 files · 8 tests · bundled sample

Load your own folder

Files are read in your browser. Only .js/.ts source is sent for analysis; node_modules and build folders are skipped.

2. What changed

src/cart/cart.test.tstest
src/cart/cart.ts
src/cart/cartEvents.ts
src/checkout/checkout.spec.tstest
src/checkout/checkout.ts
src/orders/history.test.tstest
src/orders/history.ts
src/payments/__tests__/gateway.tstest
src/payments/gateway.ts
src/pricing/discount.test.tstest
src/pricing/discount.ts
src/pricing/index.ts
src/pricing/tax.test.tstest
src/pricing/tax.ts
src/ui/CartView.test.tsxtest
src/ui/CartView.tsx
src/utils/date.ts
src/utils/money.test.tstest
src/utils/money.ts

Pick the files you changed or paste a diff, then press Analyze impact.

Or try an example

Static import analysis for JavaScript and TypeScript projects. Your code is analysed in memory and never stored.