2 ms·
developers become reliant on CI and won't run the tests until merge-time I think there's a whole lot of truth in this particular statement. I've worked with lo
by onion2k 4y ago
developers become reliant on CI and won't run the tests until merge-time
I think there's a whole lot of truth in this particular statement. I've worked with lots of devs who complete a story, commit it, and then find the tests aren't passing any more and have to do a little more work to fix what they broke. And then tery complain that either tests slow them down or that the estimate for the story was too low. Having a test suite that can be run locally, and teaching the team to use it regularly, even if it's wholly optional rather than running on a hook, improves team velocity significantly.
- verve_rat 4y agoWhy only one commit for a story? Sounds like they should be committing more often. I often fire off a commit, get notified of a test failure, and fix it in the next commit. Why wait for tests to run locally when some other computer can do it for you? (Yes, it would be nice if all tests ran in zero time, but back in the real world...)