Database content empty for second run about rspec-benchmark HOT 6 CLOSED

Hi,

Thanks for using this gem!

This gem should have no impact on how your records are saved. It has no dependency on external environment such as Rails, databases etc... It simply calls a block, the expectation, a number of times and each time it executes the block it measures the time. Therefore, the implication is that if you setup your DB once before the expectation is executed, and your foo.bar code has side effects including modifications to DB, then it is no surprise that it fails to execute correctly on the second block evaluation.

The rspec matchers perform no mutation of your database as they have no understanding of any of your code. This gem can be used in any context to execute a function. If the function is pure then you don't need to worry, however in your case you have clear DB mutations and hence keeping all the setup in the block is the only way to ensure that each block evaluation starts in the same state.

Hope this makes sense!

from rspec-benchmark.

I'm having a similar problem. Could it be because the benchmark-perf gem runs the block to be timed in a sub process?

from rspec-benchmark.

@tjwallace It could be or it could not be, I don't know. Would you have time to code up a minimal example using active record and sqlite that replicates the problem you're having and open a new issue? I would like to have something to poke around and I'm sure we can get to the bottom of it.

from rspec-benchmark.

@piotrmurach done, see issue #10

from rspec-benchmark.

@tjwallace Magic! Thank you.

from rspec-benchmark.

Thank you @tjwallace

from rspec-benchmark.