Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce per-invocation lifecycle callbacks for container templates #4320

Open
2 tasks
marcphilipp opened this issue Feb 14, 2025 · 1 comment · May be fixed by #4353
Open
2 tasks

Introduce per-invocation lifecycle callbacks for container templates #4320

marcphilipp opened this issue Feb 14, 2025 · 1 comment · May be fixed by #4353

Comments

@marcphilipp
Copy link
Member

marcphilipp commented Feb 14, 2025

Follow-up on #871.

Analoguous to BeforeAllCallback etc., new BeforeContainerTemplateInvocationCallback/AfterContainerTemplateInvocationCallback (names to be discussed) extension interfaces should be introduced as well to externalizing behavior to extensions.

Deliverables

  • Introduce BeforeContainerTemplateInvocationCallback/AfterContainerTemplateInvocationCallback extension points
  • Use them to implement field injection for @ParameterizedContainer in case TestInstance.Lifecycle.PER_CLASS is used
@marcphilipp
Copy link
Member Author

I've reduced the scope of this issue in favor of more concrete lifecycle methods for parameterized containers:

@marcphilipp marcphilipp self-assigned this Feb 27, 2025
@marcphilipp marcphilipp moved this from Todo to In Progress in Sovereign Tech Fund Feb 27, 2025
@marcphilipp marcphilipp changed the title Add per-invocation lifecycle callbacks for container templates Introduce per-invocation lifecycle callbacks for container templates Feb 27, 2025
@marcphilipp marcphilipp added this to the 5.13.0-M1 milestone Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment