It's basically a disabled cache, so putting something in does not make it
be in there

cache.set('x',1)
cache.get('x') -> nil

it's a little bit stupid but in theory it can happen with any caching
backend, so might as well include the extra test + it saves 1 cache lookup


On Thu, Jul 25, 2013 at 8:47 AM, James Alexander Rosen <
notifications@github.com> wrote:

> In test/dummy_app/test/unit/cache_test.rb:
>
> > @@ -58,6 +63,13 @@ def test_works_with_other_cache_backend
> >      Arturo::Feature.to_feature(@feature.symbol)
> >    end
> >
> > +  def test_works_with_broken_cache_backend
>
> Well, I see no reason to test for other people's code not working
> property, but the just-expired case intrigues me. I would have thought
> test_clear_cache<https://github.com/grosser/arturo/blob/0e26016f21f13e99cb1214f4f916f0192119593c/test/dummy_app/test/unit/cache_test.rb#L73>handles that.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jamesarosen/arturo/pull/62/files#r5401310>
> .
>