← Back to context Comment by anentropic 1 day ago there are tests, no?e.g. https://github.com/anomalyco/rune/tree/dev/crates/rune-kit/t... 7 comments anentropic Reply QuantumNomad_ 1 day ago Indeed. But why not run the tests in CI when merging to master? efficax 1 day ago Where I work, we've moved CI "left", all tests are run on the developers machine before merging esafak 1 day ago You're not shifting left unless you guarantee local tests always run, faithfully to production. That rarely happens. Local testing should be supplementary. We use https://hk.jdx.dev/ 3 replies → esafak 1 day ago They ain't running in CI.
QuantumNomad_ 1 day ago Indeed. But why not run the tests in CI when merging to master? efficax 1 day ago Where I work, we've moved CI "left", all tests are run on the developers machine before merging esafak 1 day ago You're not shifting left unless you guarantee local tests always run, faithfully to production. That rarely happens. Local testing should be supplementary. We use https://hk.jdx.dev/ 3 replies →
efficax 1 day ago Where I work, we've moved CI "left", all tests are run on the developers machine before merging esafak 1 day ago You're not shifting left unless you guarantee local tests always run, faithfully to production. That rarely happens. Local testing should be supplementary. We use https://hk.jdx.dev/ 3 replies →
esafak 1 day ago You're not shifting left unless you guarantee local tests always run, faithfully to production. That rarely happens. Local testing should be supplementary. We use https://hk.jdx.dev/ 3 replies →
Indeed. But why not run the tests in CI when merging to master?
Where I work, we've moved CI "left", all tests are run on the developers machine before merging
You're not shifting left unless you guarantee local tests always run, faithfully to production. That rarely happens. Local testing should be supplementary. We use https://hk.jdx.dev/
3 replies →
They ain't running in CI.