Ember 5.4: `provide` in a rendering test failing to find provideConsumeContextContainer

[runspired]

I've setup our rendering and application tests to auto-provide a store context in a beforeEach.

hooks.beforeEach(function (assert) {
  provide('store', this.owner.lookup('service:store'));
});

This is throwing the below error:

Could not find "provideConsumeContextContainer" instance in runtime environment

Which comes from here:

ember-provide-consume-context/ember-provide-consume-context/src/test-support/index.ts

Line 51 in 4d9835e

'Could not find "provideConsumeContextContainer" instance in runtime environment',

Is there something else I need to do prior to calling provide? Is this an incompatibility with our Ember Version? Something else?

[runspired]

My naive take reading the code is that there is no value for provideConsumeContextContainer until the renderer has rendered at least once since it is set here at the earliest

ember-provide-consume-context/ember-provide-consume-context/src/-private/override-glimmer-runtime-classes.ts

Line 73 in 4d9835e

new ProvideConsumeContextContainer();

but in tests, this is not guaranteed to have occurred.

[kevinkucharczyk]

@runspired would you mind providing a minimum reproduction of this? Or at least describe the minimum steps needed, I don't need a whole repo.

The addon has a few basic rendering tests for that provide helper:

ember-provide-consume-context/test-app/tests/integration/components/test-support-test.ts

Line 15 in 4d9835e

provide('my-test-context', '1');

, and I wonder if the issue you're seeing only happens in application tests.

Your assumptions seem valid to me. We'll need to defer injecting the test providers until a render has occurred, or register it outside of the environment. I'll prepare a fix next week!

[runspired]

I figured out this was only happening in application tests, not other rendering tests, and since I didn't need to setup a provider in this way for application tests I refactored my setup.

[kevinkucharczyk]

@runspired glad you found an alternative!
I'd say the recommendation here should be that the provide helper is really only meant for rendering tests. When an application test renders the whole app, it doesn't really make sense to override specific contexts - they may be nested layers deep in routes or component trees. Mocking a context there would be like mocking a specific component that renders somewhere in your tree, which isn't really how Ember apps are tested.

I could maybe see an argument for this if we think about it more like a service, rather than a component - services are often mocked in tests. But we could only globally override contexts of a particular name - we'd lose important context behavior like deeper contexts taking precedence over parent ones. Contexts act more component-like then service-like.