JDK-8091664 : Gradle: run tests from the bottom up
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: build
  • Affected Version: 8
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2013-07-17
  • Updated: 2024-11-21
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Blocks :  
Description
When a test fails in a module, gradle stops the build (which is probably fine). I don't know if the order of the modules to test is specified but locally I can see controls tests run before graphics tests. When there's something broken in graphics (scenegraph for instance), the controls tests are likely to fail and the developer will have to spend time figuring out the error is actually down in graphics. I'm particularly interested in these two modules, but in general, we should try to define testing order from the bottom layers up.
Comments
Lower priority since gradle --continue will run all tests.
10-08-2013

Note that you can run: gradle --continue test and it will run the tests from all projects even if there are failures in some of them.
18-07-2013