I think I overtook git blame ownership when I rewrote the tests earlier this year (:cry:), so I'll quickly chime in :) The reason for setting `min_cost` on these tests is to supposedly speed things up when any test case directly or indirectly trigger a `password=`. A good number of them ended up requiring it (~20 out of 23), so it was extracted to the `setup`/`teardown` hooks. This also has another small advantage – when someone add a new test case they can't "forget" to use a helper method etc to accidentally introduce a slow test.

So while I usually agree that inlining these changes is better, in this case it might be justified. Not a huge difference though.

As for the other things being discussed, I have no strong opinions one way or the other.