integration tests and using the container's Weld context to inject recursively.

[tbee]

I understand the need to have a standalone Weld container when doing unit tests, as weld-testing provides. But if you run integration tests for -say- a stateless EJB, you still have a junit test, but the test executes inside the JakartaEE container. Not all stateless services have a REST API. In that case you want the CDI of the container injecting things into the tests, so basically weld-junit5 without the weld-se context, but with wildfly's weld context.

I have been able to get a one level injection going, so an @Inject in a junit test is resolved. But the injected class does not have its @Inject resolved, those references are all null. I cannot seem to figure out how to make inject recursive.

This is a bit out of scope, but I dare to ask: any suggestions? 😄

BTW, this code does a one level deep injection:

        BeanManager beanManager = CDI.current().getBeanManager();
        CreationalContext<Object> ctx = beanManager.createCreationalContext(null);
        InjectionTarget<Object> injectionTarget = (InjectionTarget<Object>) beanManager
                .getInjectionTargetFactory(beanManager.createAnnotatedType(test.getClass()))
                .createInjectionTarget(null);
        injectionTarget.inject(test, ctx);

I have to admit that why this works is not obvious to me. For example InjectionTarget? It is injecting, so hardly a target of injection. Injector seems a more logical name. Alas.

[manovotn]

Hello

I understand the need to have a standalone Weld container when doing unit tests, as weld-testing provides. But if you run integration tests for -say- a stateless EJB, you still have a junit test, but the test executes inside the JakartaEE container. Not all stateless services have a REST API. In that case you want the CDI of the container injecting things into the tests, so basically weld-junit5 without the weld-se context, but with wildfly's weld context.

IIUIC, you may be looking for something like Arquillian testing, which can run directly against an instance of WFLY or an adapter that simulates it. Weld core itself has such tests, located under https://github.com/weld/core/tree/master/tests-arquillian
Those can run against WFLY directly (with -Dincontainer switch), or against an embedded container (by default), using https://github.com/arquillian/arquillian-container-weld
Note that I am guilty of not having delved into rewriting those tests into JUnit 5 yet so the links are to tests using Arq. and Junit 4. It should however be possible to use JUnit 5 too! You will need to look around for other projects on how to set it up I guess.

I have been able to get a one level injection going, so an @Inject in a junit test is resolved. But the injected class does not have its @Inject resolved, those references are all null. I cannot seem to figure out how to make inject recursive.
BTW, this code does a one level deep injection:

The code you linked is a CDI API way of injection into a specific target, mostly non-managed instance.
I am not sure I understand the one level deep injection though. CDI will inspect the instance you give it and attempt to inject into it where applicable. However, all injected objects have to be CDI beans as well and as such will be created/managed by CDI including injection into them.

Just to be clear, when it comes to injection into test class, if you are using weld-junit, that's done for you by the junit extension so long as the container knows required beans.

I would probably need some snippet showing what you mean by that so I can provide some more specific help :)

I have to admit that why this works is not obvious to me. For example InjectionTarget? It is injecting, so hardly a target of injection. Injector seems a more logical name. Alas.

I tend to think of it as an abstraction of the target into which you want CDI to inject. You are creating a prescription for injection into a certain type <T> and then passing in the actual instance (and context).