WildcardPatternSuite Allow searching from parent directory

[shayfdna]

Hey, i want my 'tests' folder to be alongside my 'suits' folder.
and i can't "../**/*xTest.class". can you hero please ?

also i asked on stack overflow.
https://stackoverflow.com/questions/44127825/junit-suite-from-classpath-with-categories-support
thank you

[shayfdna]

to solve this i had to get a copy of the class 'WildcardPatternSuite' and rewrite the method 'getBaseDir' to:

private static File getBaseDir(Class<?> klass) throws InitializationError {
    String rootBuildPath = klass.getProtectionDomain().getCodeSource().getLocation().getFile();
    URL klassUrl = klass.getResource(klass.getSimpleName() + ".class");
    return new File(rootBuildPath);
}

[MichaelTamm]

Hi,

would you like to create Pull Request?

[shayfdna]

i would, but this resulting for 2 tests to fail. i don't have time to understand why,
here is my fix.
(i would love to use it, thank you )

WildcardPatternSuite.java.zip

[shayfdna]

have you looked at it ?

[kevdowney]

+1 on this feature. Please submit a PR.

[MichaelTamm]

@shayfdna With your changes to getBaseDir(...) the method does no longer return the directory, where the suite class is located, but the test-classes directory.

I understand your intent, but this change would break all existing suite classes, which are inside some package and use the @WildcardPatternSuite annotation.

[shayfdna]

thanks Michal, for me parent directory of the test suite is not enough, since my project structure is complex and hierarchy is deeper then one folder

[MichaelTamm]

You can now* use: @SuiteClasses("../../../foo/**/*Test.class")

I.e. you can go as many levels up as you want (as long as all test classes are under the same test-classes directory).

• now == now if you use HEAD else whenever I have time to publish a new release ;)

[MichaelTamm]

I released JUnit Toolbox 2.4 which includes the fix for this issue.