-
-
Save cheeyeo/790118 to your computer and use it in GitHub Desktop.
# delay the GC - usage as below | |
# Spec::Runner.configure do |config| | |
..... | |
# config.before(:each) do | |
# begin_gc_deferment | |
# end | |
# config.after(:each) do | |
# reconsider_gc_deferment | |
# end | |
#end | |
DEFERRED_GC_THRESHOLD = (ENV['DEFER_GC'] || 1.0).to_f | |
@@last_gc_run = Time.now | |
def begin_gc_deferment | |
GC.disable if DEFERRED_GC_THRESHOLD > 0 | |
end | |
def reconsider_gc_deferment | |
if DEFERRED_GC_THRESHOLD > 0 && Time.now - @@last_gc_run >= DEFERRED_GC_THRESHOLD | |
GC.enable | |
GC.start | |
GC.disable | |
@@last_gc_run = Time.now | |
end | |
end |
Cucumber tests are run separately away from the Rspec framework so I don't think the above would have any effect since the spec_helper.rb file is mainly for rspec tests. What exactly are you trying to resolve with your cucumber tests - to speed it up?
yes, i had implemented jamis' GC deferral hack in test:unit with much success. was just hoping to do similar with our cucumber suite
Interesting subject to bring up. Will do some research of my own to see if something similar can be achieved for Cucumber.
Try using either Hydra or parallel_specs to run your cucumber tests to speed it up. Also worth checking out is refactoring some of your cucumber tests code to avoid creating additional objects such as logged in users for instance. From what I understand of how cucumber works, it does full stack testing so the spec_helper methods above is no good. You would need something else like parallel_specs to run your steps in multiple processes to make any difference.
I'm kinda new to cucumber. Would this help to add to my spec_helper.rb if I'm only running cucumber tests?