Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2275
>HDFS and Yarn are handled through the @BeforeClass and @AfterClass style
and they do not use custom JRunner implementation. As you have suggested, I
could keep just one or two tests for each of the modules to cut down the
running time, if that's okay with you?
Thanks! Yes, please just one test per entity (HDFS, Yarn, Kafka/Zookeeper).
Could you also convert the Kafka test to using `@BeforeClass` and
`@AfterClass`? You don't necessarily have to duplicate code. How about changing
the test base to include a method to instantiate the secure settings? I think
you'll need to add an abstract method in `KafkaTestEnvironment`, e.g.
loadSecureSettings(), then add another one in `KafkaTestBase`, e.g.
getTestEnvironmentClass(), to load the appropriate test environment
(secure/non-secure). You will have additional classes that implement these two
methods. These classes will be very short as they just overload the method.
This is cleaner although a bit more verbose.
>I am open to keep just 3 classes for each scenarios (HDFS, Yarn & Kafka)
as you have suggested but in my opinion that will defeat the idea of reusing
existing test program.
I understand but we're actually just increasing the testing time and not
gaining much from running multiple security tests for the same component.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
