[Rspec-devel] use case for: setup_once, teardown_once

[itsme213]

From: "aslak hellesoy" <aslak.hellesoy at gmail.com>

>>  - would it be appropriate to be testing expensive/slow things?
>
> Yes, but you should isolate slow code in separate classes and have a
> separate set of specs for those classes only.

If I have 5 components, and the communication channels between them are 
slow, and my acceptance test is about a round trip from outside, through all 
5, and back (possibly including things like response time): what should I 
isolate?

> This is where you should be able to use mocks for the expensive stuff,
> when running specs for the remaining 10%.

I do understand (and agree with) this advice in the context of unit testing. 
I don't see how I could apply it to an integration or acceptance test.

Thanks!