Introducing (another/additional) JavaFX TestFramework

Let me start with the statement that TestFX is somewhat the default JUnit-Testframework for JavaFX application and is what we proposed to use to all our customers and our projects until today where we introduce our own one.

There are 2 different problem vectors we have:

  • A licensing issue we have with it at TestFX is licensed under EUPL which to me as a software developer looks ok but it looks like the IP-Department at is not happy about it and refused me to use it. I don’t blame anyone but need to cope with the situation as is!
  • Implementing JUnit-Tests for OSGi-JavaFX applications: This is a pure technical issue and something we could have solved (although it would have meant to change the way TestFX works) but after having hit the licensing problem my motivation to resolve that problem was not really there

Anyways let’s look at what I’ve started to implement as a replacement for TestFX.

BestSolution FX-Test

First of all we decided for now that we don’t integrate the test-framework into e(fx)clipse but treat it as an independent entity at github and release it under EPL from there.

Writing JUnit-Tests is done by subclassing a base class (current only one available is FXComponentTest) and implementing your JUnit-Tests might look like this:

public void sample() {
  // Search with a css-selector query
  // and generated a click on the button

In contrast to TestFX, tests written with our API can not run directly but you need to decided if you want to:

  • Use a specific runner using @RunWith(FXRunner.class)
  • Use a Rule @FXTest and annotate all UI-Test methods with it

which on the plus-side means that the @Test-methods are executed on the JavaFX-UI-Thread (unlike TestFX where they are executed on another thread most like the main-thread)

For more information that a look at the project

Let me close this post saying that we are very early in the development and things are still in the flux so we are happy for any feedback we get.

This entry was posted in e(fx)clipse. Bookmark the permalink.

6 Responses to Introducing (another/additional) JavaFX TestFramework

  1. Pingback: JavaFX links of the week, August 14 | JavaFX News, Demos and Insight // FX Experience

  2. Pingback: FX-Test: JUnit-Tests für JavaFX und OSGi - JAXenter

  3. Patrice-Emmanuel SCHMITZ says:

    Just find this conversation and wonder why the Eclipse IP dept. refuses using a module under the EUPL licence, knowing that the Eclipse licence is listed as downstream compatible with the EUPL (= you may merge code covered by the EUPL in another project covered by Eclipse).
    Any reason for this decision ???

    • Tom Schindl says:

      IIRC there was one problematic clause and board of directors refused to add EUPL as an approved license. I have no further information why exactly.

  4. Marcelo says:

    Hi Tom,
    I’ve been trying to grab the binaries from and but my browser can’t connect to them. Is the server running?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.