-
Bug
-
Resolution: Fixed
-
P4
-
jfx11
-
b09
We have a few different patterns in use for system tests that need to startup the FX runtime, and in most cases, show a stage.
We should consider modifying the tests to use as consistent a pattern as possible to avoid subtle difference that could affect test stability.
```
@BeforeClass
public static void initFX() throws InterruptedException {
startupLatch = new CountDownLatch(1);
// Start the Application
new Thread(() -> Application.launch(TestApp.class, (String[])null)).start();
Assert.assertTrue(startupLatch.await(15, TimeUnit.SECONDS));
}
```
NOTE: double check that the Application being launched has this code it its start() method:
```
stage.setOnShown(l -> {
Platform.runLater(() -> startupLatch.countDown());
});
```
We should consider modifying the tests to use as consistent a pattern as possible to avoid subtle difference that could affect test stability.
```
@BeforeClass
public static void initFX() throws InterruptedException {
startupLatch = new CountDownLatch(1);
// Start the Application
new Thread(() -> Application.launch(TestApp.class, (String[])null)).start();
Assert.assertTrue(startupLatch.await(15, TimeUnit.SECONDS));
}
```
NOTE: double check that the Application being launched has this code it its start() method:
```
stage.setOnShown(l -> {
Platform.runLater(() -> startupLatch.countDown());
});
```
- blocks
-
JDK-8296919 Make system tests that detect memory leaks more robust by using JMemoryBuddy utility
- Resolved
- relates to
-
JDK-8199614 [macos] ImageCursor.getBestSize() throws NullPointerException
- Resolved
-
JDK-8176776 Linux: Intermittent unit test failures in window position, resize tests
- Open