[jonstjohn]

Great tips - thanks! In addition to some slow-running tests, we do have a lot of test duplication. It's probably time to step back and evaluate what tests are overlapping functionality.

Do you use any tools to facilitate your workflow on fixing tests? Typically, we run a regression build on a branch and may find a half dozen failures. With 4-5 developers on a distributed team, we've built a utility for 'checking out' and marking a test as fixed (to be verified on the next build) but haven't seen any similar functionality in the CI systems we use.

[trcollinson]

Nothing slows down a test suite like test duplication! I would definitely suggest a refactor, it will help. But remember you don't eat an elephant all at once, take it one bite at a time. A small amount but consistent level of test refactoring will go a long well.

It sounds like you have a good workflow to me but obviously you feel you have a problem or you wouldn't be posting here. I've working in environments where the failing tests are assigned out on an individual basis, where there was a bouncer who took on all broken tests, and where each individual engineer would run the tests often enough that they would just fix what they broke. The latter method is my favorite. But it is not always feasible.

I guess the answer really depends on your environment. I would be very happy to give my advise (for what it's worth). If you would like you may email me. My address is my Hacker News username at googles very large and famous free email service.