Unexpected: abstract test classes are run ...
fastegal at swingempire.de
Tue Oct 15 12:17:19 UTC 2019
Zitat von Kevin Rushforth <kevin.rushforth at oracle.com>:
> Our convention, which is codified in build.gradle (but not
> documented well), is that the name of any concrete unit test class
> must end with exactly `Test`. Similarly, the name of any abstract
> super class or utility class should not end with `Test`. It's a
> little clunky, but dates back to the very early port of JavaFX build
> to gradle.
ahh ... faintly remember those days, think we used the same/similar
convention in SwingX :)
> Or are you seeing something else?
no - works with renaming, thanks
> As for the version of junit, we could consider updating to a newer
> version (it would need us to do a third-party approval), if there
> were enough benefit. It would be behind a few other things for
if there are other niceties (apart from the name parameter in
parameterized tests) not available in 4.8.2, I will stumble across
them, I always do sooner or later <p>
> -- Kevin
> On 10/15/2019 4:48 AM, Jeanette Winzenburg wrote:
>> .. with gradle :controls:test
>> Maybe related to the outdated version (4.8.2 of junit) as well as
>> the problem with missing name property (of Parameterized? Don't
>> know, though.
>> The workaround seems to be to @Ignore abstract tests - descendants
>> are run as expected.
More information about the openjfx-dev