@moollaza I think I know why I was (and probably still am) confused.  I assumed that the `is_cached` setting in the test file was to tell the test infrastructure how I expected the value to be set in the responses.  Thus, I stopped setting the value in the package, but left it untouched in the test.  I expected that if I stopped setting on both sides it would both set and expect the default, which doesn't tell me very much about how that default is set.

I would have been much less confused if I had stopped setting it and it returned some true (but not "1") value as opposed to "0".


Given the discussion here, it seems likely that I am just not _supposed_ to care about/test how `is_cached` is set trusting that the default configuration will make sense in whichever environment it finds itself.  For example, maybe there's a predicate to determine if it was explicitly set before using the actual value or something?