README.md in ttl_memoizeable-0.3.0 vs README.md in ttl_memoizeable-0.4.0

@@ -149,21 +149,45 @@
 application_config.config # => {...} Redis/JSON.parse will be called
 ```
 
 ## Testing a TTLMemoized Method
 
-You likely don't want to test the implementation of this library, but the logic of your memoized method. In that case you probably want "fresh" data on every invocation of the method. There are two approaches, depending on your preference of flavor.
+You likely don't want to test the implementation of this library, but the logic of your memoized method. In that case you probably want "fresh" data on every invocation of the method. There are a few approaches, depending on your preference of flavor.
 
 1. Use the reset method provided for you. It follows the pattern of `reset_memoized_value_for_#{method_name}`. Note that this will only reset the value for the current thread, and shouldn't be used to try and create consistent data state across processes.
 ```ruby
 def test_config
   ApplicationConfig.reset_memoized_value_for_config # or in a setup method or before block if available
 
   assert_equal {...}, ApplicationConfig.config
 end
 ```
 
-2. Conditionally TTL memoize the method based on test environment or some other condition.
+2. Disable ttl memoization globally in your tests. This will prevent a memoized value from ever being returned.
+
+```ruby
+TTLMemoizeable.disable!
+```
+
+3. Reset ttl memoization values before/after your test runs.
+
+```ruby
+# RSpec
+RSpec.configure do |config|
+  config.around { TTLMemoizeable.reset!; _1.run; TTLMemoizeable.reset! }
+end
+
+# minitest
+def setup
+  TTLMemoizeable.reset!
+end
+
+def teardown
+  TTLMemoizeable.reset!
+end
+```
+
+4. Conditionally TTL memoize the method based on test environment or some other condition.
 ```ruby
 def config
   JSON.parse($redis.get("some_big_json_string"))
 end