Reload controller class with caching callbacks

10 views
Skip to first unread message

Andrew Vit

unread,
Nov 27, 2012, 5:42:24 PM11/27/12
to rubyonra...@googlegroups.com
I'm trying to write an RSpec helper for testing cached actions:

https://github.com/avit/rspec-rails-caching/

How it works is visible in lib/rspec-rails-caching.rb, but to outline the 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 environment.
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 the 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 loaded inside or outside the caching example group. How can I force the class to reload "cleanly" to ensure the caching callbacks get run? Or is there a better solution?
Reply all
Reply to author
Forward
0 new messages