Hi @ikysil
CdiJUnit5Extension.createTestInstance() seems to need something like

if (testConfiguration == null) {
    beforeAll(extensionContext);
}

to avoid NullPointerException with maven-surefire-plugin

Hi @graben

... CdiJUnit5Extension.createTestInstance() seems to need something like

if (testConfiguration == null) {
    beforeAll(extensionContext);
}

to avoid NullPointerException with maven-surefire-plugin

I don't see this happening in neither of the modules.
Would you mind to provide a reproducer?

Hi @graben

... CdiJUnit5Extension.createTestInstance() seems to need something like

if (testConfiguration == null) {
    beforeAll(extensionContext);
}

to avoid NullPointerException with maven-surefire-plugin

I don't see this happening in neither of the modules. Would you mind to provide a reproducer?

Sure. test.zip
It seems that the implementing interface for logging is causing surefire to call createTestInstance earlier than expected!?

The presence of the @TestInstance(PER_CLASS) annotation changes the order of the extension callbacks.

@ikysil: Is an automatic synchronization between @TestInstance and @Isolation planed? It might cause issues if not.

Let's have a discussion #290 and then implement whatever is decided.