JUnit 6.0.1 · org.junit.jupiter.params.InstancePostProcessingClassTemplateFieldInjector

Modifier and Type	Field and Description
private final EvaluatedArgumentSet	arguments
private final int	invocationIndex
private final ResolutionCache	resolutionCache
private final ResolverFacade	resolverFacade

Access	Constructor and Description
pack-priv	InstancePostProcessingClassTemplateFieldInjector(ResolverFacade resolverFacade, EvaluatedArgumentSet arguments, int invocationIndex, ResolutionCache resolutionCache)

Modifier and Type	Method and Description
public TestInstantiationAwareExtension.ExtensionContextScope	getTestInstantiationExtensionContextScope(ExtensionContext rootContext) Overrides default org.junit.jupiter.api.extension.TestInstantiationAwareExtension.getTestInstantiationExtensionContextScope. Determine whether this extension should receive a test-method scoped `ExtensionContext` during the instantiation of test classes or processing of test instances.
public void	postProcessTestInstance(Object testInstance, ExtensionContext extensionContext) Implements org.junit.jupiter.api.extension.TestInstancePostProcessor.postProcessTestInstance. Callback for post-processing the supplied test instance.

Field Detail

arguments	back to summary
private final EvaluatedArgumentSet arguments

invocationIndex	back to summary
private final int invocationIndex

resolutionCache	back to summary
private final ResolutionCache resolutionCache

resolverFacade	back to summary
private final ResolverFacade resolverFacade

Constructor Detail

InstancePostProcessingClassTemplateFieldInjector	back to summary
pack-priv InstancePostProcessingClassTemplateFieldInjector(ResolverFacade resolverFacade, EvaluatedArgumentSet arguments, int invocationIndex, ResolutionCache resolutionCache)

Method Detail

getTestInstantiationExtensionContextScope back to summary

getTestInstantiationExtensionContextScope	back to summary
public TestInstantiationAwareExtension.ExtensionContextScope getTestInstantiationExtensionContextScope(ExtensionContext rootContext) Overrides default org.junit.jupiter.api.extension.TestInstantiationAwareExtension.getTestInstantiationExtensionContextScope. Doc from org.junit.jupiter.api.extension.TestInstantiationAwareExtension.getTestInstantiationExtensionContextScope. Determine whether this extension should receive a test-method scoped `ExtensionContext` during the instantiation of test classes or processing of test instances. If an extension returns `TEST_METHOD` from this method, methods defined in the following extension APIs will be called with a test-method scoped `ExtensionContext` instead of a test-class scoped context. Note, however, that a test-class scoped context will always be supplied if the `PER_CLASS` test instance lifecycle is used. `InvocationInterceptor`: only the `interceptTestClassConstructor(...)` method `ParameterResolver`: only when resolving constructor parameters `TestInstancePreConstructCallback` `TestInstancePostProcessor` `TestInstanceFactory` When a test-method scoped `ExtensionContext` is supplied, implementations of the above extension APIs will observe the following differences. `getElement()` may refer to the test method. `getTestClass()` may refer to a nested test class. For `TestInstancePostProcessor`, use `testInstance.getClass()` to get the test class associated with the supplied instance. For `TestInstanceFactory` and `TestInstancePreConstructCallback`, use `TestInstanceFactoryContext#getTestClass()` to get the class under construction. For `ParameterResolver`, when resolving a parameter for a constructor, ensure that the `Executable` is a `Constructor`, and then use `constructor.getDeclaringClass()` to get the test class associated with the constructor. `getTestMethod()` is no longer empty, unless the `PER_CLASS` test instance lifecycle is used. If the extension adds a `CloseableResource` or `AutoCloseable` to the `Store` (unless the `junit.jupiter.extensions.store.close.autocloseable.enabled` configuration parameter is set to `false`), then the resource will be closed just after the instance is destroyed. Extensions can now access data previously stored by a `TestTemplateInvocationContext`, unless the `PER_CLASS` test instance lifecycle is used. Note The behavior which is enabled by returning `TEST_METHOD` from this method will become the default in future versions of JUnit. To ensure forward compatibility, extension authors are therefore advised to opt into this feature, even if they do not require the new functionality. Annotations @Override

public TestInstantiationAwareExtension.ExtensionContextScope getTestInstantiationExtensionContextScope(ExtensionContext rootContext)

Overrides default org.junit.jupiter.api.extension.TestInstantiationAwareExtension.getTestInstantiationExtensionContextScope.

Doc from org.junit.jupiter.api.extension.TestInstantiationAwareExtension.getTestInstantiationExtensionContextScope.

Determine whether this extension should receive a test-method scoped ExtensionContext during the instantiation of test classes or processing of test instances.

If an extension returns TEST_METHOD from this method, methods defined in the following extension APIs will be called with a test-method scoped ExtensionContext instead of a test-class scoped context. Note, however, that a test-class scoped context will always be supplied if the PER_CLASS test instance lifecycle is used.

InvocationInterceptor: only the interceptTestClassConstructor(...) method
ParameterResolver: only when resolving constructor parameters
TestInstancePreConstructCallback
TestInstancePostProcessor
TestInstanceFactory

When a test-method scoped ExtensionContext is supplied, implementations of the above extension APIs will observe the following differences.

getElement() may refer to the test method.
getTestClass() may refer to a nested test class.
- For TestInstancePostProcessor, use testInstance.getClass() to get the test class associated with the supplied instance.
- For TestInstanceFactory and TestInstancePreConstructCallback, use TestInstanceFactoryContext#getTestClass() to get the class under construction.
- For ParameterResolver, when resolving a parameter for a constructor, ensure that the Executable is a Constructor, and then use constructor.getDeclaringClass() to get the test class associated with the constructor.
getTestMethod() is no longer empty, unless the PER_CLASS test instance lifecycle is used.
If the extension adds a CloseableResource or AutoCloseable to the Store (unless the junit.jupiter.extensions.store.close.autocloseable.enabled configuration parameter is set to false), then the resource will be closed just after the instance is destroyed.
Extensions can now access data previously stored by a TestTemplateInvocationContext, unless the PER_CLASS test instance lifecycle is used.

Note

The behavior which is enabled by returning TEST_METHOD from this method will become the default in future versions of JUnit. To ensure forward compatibility, extension authors are therefore advised to opt into this feature, even if they do not require the new functionality.

Annotations

@Override

postProcessTestInstance back to summary

postProcessTestInstance	back to summary
public void postProcessTestInstance(Object testInstance, ExtensionContext extensionContext) Implements org.junit.jupiter.api.extension.TestInstancePostProcessor.postProcessTestInstance. Doc from org.junit.jupiter.api.extension.TestInstancePostProcessor.postProcessTestInstance. Callback for post-processing the supplied test instance. By default, the supplied `ExtensionContext` represents the test class that's being post-processed. Extensions may override `getTestInstantiationExtensionContextScope` to return `TEST_METHOD` in order to change the scope of the `ExtensionContext` to the test method, unless the `PER_CLASS` lifecycle is used. Changing the scope makes test-specific data available to the implementation of this method and allows keeping state on the test level by using the provided `Store` instance. Note the `ExtensionContext` supplied to a `TestInstancePostProcessor` will always return an empty `java.util.Optional` value from `getTestInstance()`. A `TestInstancePostProcessor` should therefore only attempt to process the supplied `testInstance`. Annotations @Override

public void postProcessTestInstance(Object testInstance, ExtensionContext extensionContext)

Implements org.junit.jupiter.api.extension.TestInstancePostProcessor.postProcessTestInstance.

Doc from org.junit.jupiter.api.extension.TestInstancePostProcessor.postProcessTestInstance.

Callback for post-processing the supplied test instance.

By default, the supplied ExtensionContext represents the test class that's being post-processed. Extensions may override getTestInstantiationExtensionContextScope to return TEST_METHOD in order to change the scope of the ExtensionContext to the test method, unless the PER_CLASS lifecycle is used. Changing the scope makes test-specific data available to the implementation of this method and allows keeping state on the test level by using the provided Store instance.

Note

the ExtensionContext supplied to a TestInstancePostProcessor will always return an empty java.util.Optional value from getTestInstance(). A TestInstancePostProcessor should therefore only attempt to process the supplied testInstance.

Annotations

@Override

pack-priv Class InstancePostProcessingClassTemplateFieldInjector

Field Summary

Constructor Summary

Method Summary

Field Detail

Constructor Detail

Method Detail