Rails removed returning but Faker brought it in again
We wondered why our specs were NOT failing even we hadn’t removed all returnings and replaced them by tap in our current Rails 3 rc2 project. The solution was that the faker, the fake data generation library, is patching Object and introducing it’s own version of returning. This is why I believe in slim and clean test-frameworks, that don’t pollute core objects.
