Forum: Ruby on Rails Reload controller class with caching callbacks

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Andrew V. (Guest)
on 2012-11-28 00:43
(Received via mailing list)
I'm trying to write an RSpec helper for testing cached actions:

How it works is visible in lib/rspec-rails-caching.rb, but to outline
setup process:

1. Define the global RAILS_CACHE constant (i.e. Rails.cache) to a
CacheStore object that handles recording.
2. Turn on perform_caching which is normally false in the test
3. Reload the described controller.

Reloading the controller class is necessary because the cache callbacks
(after process_action) are metaprogrammed into the class, and they don't
get added when the class is loaded while
ActionController::Base.perform_caching is false. (These are the numbered
methods that look like WidgetsController#_callback_after_2961)

This helper seems to be mostly working. By "mostly" I mean my spec will
pass/fail correctly based on the expectations when I run individual
examples INSIDE my caching block. The problem is that if I run the whole
spec file with examples that are OUTSIDE my caching block too, then the
controller's caching callbacks don't get triggered. I've stepped through
process_action in the debugger and I can't figure out what is the
difference between the two scenarios. I've confirmed that both have:

1. perform_caching is true
2. The cache_store is my TestStore object
2. The _callback_after_2961 metaprogrammed caching method is defined on
controller class
3. The callback method shows up in the _process_action_callbacks chain

Still, there seems to be some difference whether the class is first
inside or outside the caching example group. How can I force the class
reload "cleanly" to ensure the caching callbacks get run? Or is there a
better solution?
This topic is locked and can not be replied to.