What is the argument against using before, let and subject in RSpec tests? [closed]

Answer 1

My thoughts...

1. By using context, before, let, let! Test suit performs better (run faster)
2. By using this constructs one can create shared contexts using same idea of inheritance, so one can override what's needed on specific situations
3. The powerful shoulda matchers relies on subject in order to work
4. The rails specific type of specs (controller, model) relies on let, before and context behind the scene
5. Let is lazy load, it does not represent oversharing if is never referenced within specific tests, meaning that even if an it has access to 100 lets, but it only uses 1, the other 99 never gets computed at all
6. Is not only the test code what a developer have to read to understand the test suit, is also the output of the test suit when running, it gives a lot of sense to what is being tested
7. I agree on before(:all) obfuscates a lot of dependencies, but for performance reason I will use it if needed