Today when I walked past another development team's Scrum board, I happened to notice that they had a card for "refactor tests". This made me happy. Too many developers out there are keen on refactoring code, but not on paying attention to their tests. This was part of my motivation for writing Test::Kit and Test::Most. You don't want to have a bunch of boilerplate at the top of all of your test modules, do you? No, you don't. Keep 'em simple, stupid!
Paying attention to code quality in test programs is at least as important as paying attention to code quality in the rest of your software, though in my experience, test quality usually gets short-changed. The main difference is that test programs often have data while regular ones don't. That makes managing them a bit more tricky. I've always been terribly ambivalent about the best way to manage this data. I should really look into this more.
The core problem with managing this data: