Re:Launch HN: StarSling (YC P25) – Self-improving CI for age...
by emscb on Tuesday November 17, 2026 @09:46PM
(#50541218)
When I trimmed my tests, I looked for ones that could be merged. Many unit tests shared the same setup and teardown, so when I merged their middle parts, that setup and teardown only had to run once. Even after merging, the tests still had to stay independent of execution order, so I checked that. In another case, some infrastructure checks were repeated across tests in one folder. For example, “the app needs environment variable A at startup” is already a test of its own, but every application-layer test also asserted it at the start. I kept that check in one place instead.
Re:Launch HN: StarSling (YC P25) – Self-improving CI for age...
by slaser79 on Wednesday November 18, 2026 @07:21AM
(#50545437)
The parity check on test IDs plus the cost cap is a good deterministic checker. For trimming tests, where judgment comes in, I'd have a separate reviewer agent decide it and not the one that proposed the change.
Re-sharding is allowed because it only changes where tests run, not what runs. It has the same sort of parity check as other patches but it also has a cost check to make sure the change doesn't increase runner time by more than 5% by default. We added the cost check after seeing the agents crush wall clock while 10x'ing costs on some test :)
Judging whether or not a test should be trimmed isn't something our agents do yet, because as you alluded to, it's hard. But we're working on it! If you have any ideas or an approach that's worked for you, would love to hear it.