Matous Jobanek

I think that we already know what is test class - classes contained in the list to be executed. In other words, all classes scanned/filtered by surefire based on the...

no, this is another issue - different use case. Currently, it supports only one custom provider. This task is to support multiple providers.

In Che, we are fine with this definition as well. When we call the ST tool, we already know which test classes have been chosen for the execution. In other...

One technical comment regarding to the code of [`AffectedTestsDetector.getTests`](https://github.com/arquillian/smart-testing/blob/master/strategies/affected/src/main/java/org/arquillian/smart/testing/strategies/affected/AffectedTestsDetector.java#L70) and the method [`TestVerifier.isCore`](https://github.com/arquillian/smart-testing/blob/master/core/src/main/java/org/arquillian/smart/testing/api/TestVerifier.java#L38) the method returns just a negation of the check if the class is a test class. However,...

Of course that from the surefire point of view it is not a test. But surefire doesn't use the non-test classes for some additional analysis as we do. My question...

I have one idea how to improve the performance: The calculations (scm) would be executed in a separated thread, so the main thread wouldn't be blocked and could continue with...

@lordofthejars IIRC you have some big project with a lot of test classes. Is it [AssertJ](https://github.com/joel-costigliola/assertj-core) or something else?

> if affected strategy is enabled If we don't want to detect which strategies are activated in the maven extension phase, then we cannot create this kind of chain. Instead...

The reason is in the surefire plugin magic. To provide our own implementation of a provider, we need to specify the dependency in the surefire plugin part. Then surefire finds...

Technically nothing. The benefit is having a lot of states of one project that can be examined at one time = during one (longer) execution. Also, if we knew that...