You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm creating an extension for running tests to different environments.
The test class has an annotation that has all information to discover which environments should be tested. The annotation is a consul service name. I discover all the environments with the BeforeAllCallback and save them for later in the store that is in the ExtensionContext. (step 1)
The test class has a @TestTemplate test. With the TestTemplateInvocationContextProvider I generate a stream of TestTemplateInvocationContextObjects. In the object I have overridden the getDisplayName(final int invocationIndex). The stream is based on the list of environments I have created in step 1. (Let's call this step 2).
Then what happens is that the class will be instantiated with the TestInstanceFactory interface. The method createTestInstance(TestInstanceFactoryContext factoryContext, ExtensionContext extensionContext) is called; but here starts the problem: I have no indication for which test-template-instance the class is instantiated, so I have no reference for which environment this object is instantiated. (Step 3). I need to know why the object is to be instantiated, so I can call the constructor with the consul-information from step 1.
I made a 'dirty hack' to just have an internal counter to give every construction another environment; which works okay for 1 @TestTemplate, but if you have more than one and do it multithreaded, the environments are divided totally wrong: Test1-Env1 gets Env1, Test2-Env1 get Env2, Test2-Env2 gets Env3, Test1-Env2 gets Env4.
To run the test I use interceptTestTemplateMethod(Invocation<Void> invocation, ReflectiveInvocationContext<Method> invocationContext, ExtensionContext extensionContext) because I need to have initialization around the actual run of the test method.
What I need and can't find is that I need some sort of connection between the stream of tests that are created in step 2 and the construction of the test object for that specific test in step 3.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm creating an extension for running tests to different environments.
The test class has an annotation that has all information to discover which environments should be tested. The annotation is a consul service name. I discover all the environments with the
BeforeAllCallback
and save them for later in the store that is in theExtensionContext
. (step 1)The test class has a
@TestTemplate
test. With theTestTemplateInvocationContextProvider
I generate a stream ofTestTemplateInvocationContext
Objects. In the object I have overridden thegetDisplayName(final int invocationIndex)
. The stream is based on the list of environments I have created in step 1. (Let's call this step 2).Then what happens is that the class will be instantiated with the
TestInstanceFactory
interface. The methodcreateTestInstance(TestInstanceFactoryContext factoryContext, ExtensionContext extensionContext)
is called; but here starts the problem: I have no indication for which test-template-instance the class is instantiated, so I have no reference for which environment this object is instantiated. (Step 3). I need to know why the object is to be instantiated, so I can call the constructor with the consul-information from step 1.I made a 'dirty hack' to just have an internal counter to give every construction another environment; which works okay for 1
@TestTemplate
, but if you have more than one and do it multithreaded, the environments are divided totally wrong: Test1-Env1 gets Env1, Test2-Env1 get Env2, Test2-Env2 gets Env3, Test1-Env2 gets Env4.To run the test I use
interceptTestTemplateMethod(Invocation<Void> invocation, ReflectiveInvocationContext<Method> invocationContext, ExtensionContext extensionContext)
because I need to have initialization around the actual run of the test method.What I need and can't find is that I need some sort of connection between the stream of tests that are created in step 2 and the construction of the test object for that specific test in step 3.
Beta Was this translation helpful? Give feedback.
All reactions