Any body here have any experience with this sort of situation?
Our team of 10 devs supports a legacy monolithic Rails app with almost no test coverage. So, in order to be refactor friendly we decided to write feature tests to cover all of our controller actions. That way we could refactor heavily without breaking or rewriting tests much.
It sounded boring so I decided to make it a bit more fun by gamifying the whole task. We're writing our controller actions onto Post It notes and putting them up on the board where the devs can grab one and when they're done writing tests to cover those actions they can put it in a column under their name. And then in the end, I don't know, free beers.
The challenge with this is that we have lots of controllers. So I wrote this gem to automate the action grouping and print out process. What this gem does is introspect on the app's controllers, grabs all the public actions, counts their lines of code, and then groups them together so that all Post It notes have a roughly equal total lines of code.
So I thought that was neat and wanted to share. Here's the code: https://github.com/DiegoSalazar/post_it_note_actions
3 comments
Fun ways to split up boring tasks among a dev team | Heykuki News