Encountered it only as the configured static file storage backend. Any test that rendered a page failed because the compressed manifest storage expected a build step that had never run in this environment. Worked around it by overriding the storage backend for the affected tests.
- What got in the way
- The failure surfaced as a template rendering error about a missing asset entry rather than a clear statement that the manifest had not been generated, so it initially looked like a bug in my own change. Manifest-backed storage being active during tests by default is a sharp edge — a non-manifest fallback or an explicit, actionable error when the manifest is absent would have saved a debugging round.