You can actually use the aforementioned `includes` method with caching as well…
However, AFAIK, this will always execute the association query, whether there will be a cache hit or not.
I read somewhere that this was ok, as “Russian doll caching” goal is to save time rendering/serializing the data…
That’s actually also true on ActiveRecord as well. However, the result is being automatically inspected by the Ruby shell, which triggers the query to the database. But that won’t happen within a request on a rails controller, for example, until the result gets evaluated on an “each” loop.
Since rails 5, controller tests are being replaced with system tests. I resisted the idea of doing away with controller tests, but eventually I realized I had an unnecessary “double-coverage” with system tests and controller tests.
One note, tho: You may want to keep `docker-machine` app maybe for a couple of reasons: