Different @InjectWith IInjectorProvider types result in failures when ran in the same test session

[trancexpress]

As the title goes, if I mix the IInjectorProvider types used in tests of the test suites, I get obscure errors. I assume, due to the injection not being done right / registries not being setup right.

Is this an expected issue, that needs to be worked around by not mixing injector providers in the same test session? Or its a flaw in the IInjectorProvider implementation? Unfortunately I don't have a reproduction snippet outside of our product.

[cdietrich]

Can you give an example what you mean by mix

and what kind of error do you see

junit 4 or 5 or 4 in 5

Osgi/ui or standalone

[trancexpress]

Can you give an example what you mean by mix

I mean, one test case uses one IInjectorProvider type (specified via @InjectWith), the next test case uses a different one. Something is not cleaned-up properly after the tests, since e.g. the first test case can cause errors in the next test cases.

The first test case in this case, has a runtime module that causes errors in DSL generation.

and what kind of error do you see

E.g.:

org.eclipse.xtext.parser.ParseException: java.lang.IllegalStateException: Unresolved proxy http://www.....com/.../.../...#//.... Make sure the EPackage has been registered.
	at org.eclipse.xtext.parser.antlr.AbstractAntlrParser.doParse(AbstractAntlrParser.java:106)
	at org.eclipse.xtext.parser.antlr.AbstractAntlrParser.parse(AbstractAntlrParser.java:85)
	...
	at org.eclipse.xtext.parser.AbstractParser.parse(AbstractParser.java:34)
	at org.eclipse.xtext.resource.XtextResource.doLoad(XtextResource.java:178)
	at org.eclipse.xtext.linking.lazy.LazyLinkingResource.doLoad(LazyLinkingResource.java:114)
	...
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1563)
	at org.eclipse.xtext.testing.util.ResourceHelper.resource(ResourceHelper.java:57)
	at org.eclipse.xtext.testing.util.ParseHelper.parse(ParseHelper.java:50)
	at org.eclipse.xtext.testing.util.ParseHelper.parse(ParseHelper.java:73)
	...
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
Caused by: org.eclipse.emf.common.util.WrappedException: java.lang.IllegalStateException: Unresolved proxy http://www....com/.../.../...#//.... Make sure the EPackage has been registered.
	at org.eclipse.xtext.parser.antlr.AbstractInternalAntlrParser.parse(AbstractInternalAntlrParser.java:617)
	at org.eclipse.xtext.parser.antlr.AbstractAntlrParser.doParse(AbstractAntlrParser.java:103)
	... 16 more
Caused by: java.lang.IllegalStateException: Unresolved proxy http://www....com/.../.../...#//.... Make sure the EPackage has been registered.
	at org.eclipse.xtext.parser.DefaultEcoreElementFactory.create(DefaultEcoreElementFactory.java:59)
	at org.eclipse.xtext.parser.antlr.AbstractInternalAntlrParser.forceCreateModelElement(AbstractInternalAntlrParser.java:722)
	...
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at org.eclipse.xtext.parser.antlr.AbstractInternalAntlrParser.parse(AbstractInternalAntlrParser.java:594)
	... 17 more

junit 4 or 5 or 4 in 5

JUnit 5. The same test suite with JUnit 4 has no errors.

Osgi/ui or standalone

Standalone. I've not checked with UI/Eclipse execution.

[cdietrich]

as i have never used junit 5 productive i am not sure if the extension will be properly started and showdown into the injector. can you debug this?

[cdietrich]

hmmm we call restoreRegistry
so this should (tm) work.
maybe its called tooo late

@szarnekow @tivervac are you using junit5 in a multi language setup

[szarnekow]

Yes, we use this all the time but our injector providers setup the registries for all used languages and inject into the test for a single language.