Hi all,
I just recognized that @MonoMeecrowaveConfig has no annotation attributes to
configure the container.
I understand that configuration of the container does not make sense in the
simple scenario (adding @MonoMecrowaveConfig to each test class),
since can't handle different configurations for different test classes.
However in the more sophisticated scenario of using JUnit 5 meta annotations it
would perfectly make sense,
since the user would have the configuration at one place again.
The user could define annotations like
@Testable
@Tag("UnitTest")
@MonoMeecrowaveConfig(scanningIncludes...)
public @interface UnitTest {}
and for the integration tests another annotation with other scanningIncludes
like
@Testable
@Tag("IntegrationTest")
@MonoMeecrowaveConfig(scanningIncludes...)
public @interface IntegrationTest {}
The user could then configure different run configurations for different JUnit
tags and start different containers.
My proposal is: We add the config options of @MeecrowaveConfig to
@MonoMeecrowaveConfig and when we start the container we store the annotation
in the mono base. When a second test with a different config is found, it fails
with an appropriate failure.
Wdyt?
Cheers,
Arne
OPEN KNOWLEDGE GmbH
Poststraße 1, 26122 Oldenburg
Mobil: +49 151 - 108 22 942
Tel: +49 441 - 4082-154
Fax: +49 441 - 4082-111
arne.limb...@openknowledge.de
www.openknowledge.de <https://www.openknowledge.de/>
Registergericht: Amtsgericht Oldenburg, HRB 4670
Geschäftsführer: Lars Röwekamp, Jens Schumann
Treffen Sie uns auf kommenden Konferenzen und Workshops:
Zu unseren Events<https://www.openknowledge.de/event/>
