EasyFXML - JUnit

A simple-to-use and boilerplate free JavaFX library.

License	License The Apache License, Version 2.0
Categories	Categories JUnit Unit Testing
GroupId	GroupId moe.tristan
ArtifactId	ArtifactId easyfxml-junit
Last Version	Last Version 3.3.0
Release Date	Release Date Aug 28, 2019
Type	Type jar
Description	Description EasyFXML - JUnit A simple-to-use and boilerplate free JavaFX library.
Project URL	Project URL https://tristan971.github.io/EasyFXML/easyfxml-junit/
Source Code Management	Source Code Management http://github.com/Tristan971/EasyFXML/tree/3.3.0/easyfxml-junit

Download easyfxml-junit

Filename	Size
easyfxml-junit-3.3.0.pom
easyfxml-junit-3.3.0.jar	6 KB
easyfxml-junit-3.3.0-sources.jar	3 KB
easyfxml-junit-3.3.0-javadoc.jar	400 KB
Browse

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/moe.tristan/easyfxml-junit/ -->
<dependency>
    <groupId>moe.tristan</groupId>
    <artifactId>easyfxml-junit</artifactId>
    <version>3.3.0</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/moe.tristan/easyfxml-junit/
implementation 'moe.tristan:easyfxml-junit:3.3.0'

Gradle Kotlin

// https://jarcasting.com/artifacts/moe.tristan/easyfxml-junit/
implementation ("moe.tristan:easyfxml-junit:3.3.0")

Apache Buildr

'moe.tristan:easyfxml-junit:jar:3.3.0'

Apache Ivy

<dependency org="moe.tristan" name="easyfxml-junit" rev="3.3.0">
  <artifact name="easyfxml-junit" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='moe.tristan', module='easyfxml-junit', version='3.3.0')
)

Scala SBT

libraryDependencies += "moe.tristan" % "easyfxml-junit" % "3.3.0"

Leiningen

[moe.tristan/easyfxml-junit "3.3.0"]

Dependencies

compile (8)

Group / Artifact	Type	Version
org.testfx : testfx-core	jar	4.0.15-alpha
org.testfx : testfx-junit	jar	4.0.15-alpha
org.testfx : openjfx-monocle	jar	jdk-11+26
org.springframework.boot : spring-boot-starter	jar	2.1.7.RELEASE
org.springframework.boot : spring-boot-configuration-processor	jar	2.1.7.RELEASE
org.springframework.boot : spring-boot-autoconfigure-processor	jar	2.1.7.RELEASE
io.vavr : vavr	jar	0.9.2
org.awaitility : awaitility	jar	3.1.6

test (4)

Group / Artifact	Type	Version
org.springframework.boot : spring-boot-starter-test	jar	2.1.7.RELEASE
org.assertj : assertj-core	jar	3.11.1
org.reflections : reflections	jar	0.9.11
org.hamcrest : hamcrest-library	jar	1.3

Project Modules

There are no modules declared in this project.

This project is archived

I do not realistically have the time to take care of this project, unfortunately. It originally was built along a Twitter client GUI application, and they co-evolved. But that was almost 2 years ago, and Twitter has since essentially made 3rd-party clients impossible...

Thanks for checking it out still! Hope you find a more supported alternative!

A collection of tools and libraries for easier development on the JavaFX platform

EasyFXML is an opinionated set of tools aiming to simplify development of robust and modular JavaFX applications.

The project is divided in multiple modules (each explicitly opt-in apart from the eponym core one). Feel free to have a look around:

EasyFXML MVC framework for declarative definition and reuse of components
EasyFXML - JUnit Async-first testing infrastructure for JavaFX components
EasyFXML - Docker Docker image for easy setup of CI for JavaFX applications
EasyFXML - FXKit Ready-made boilerplate for common component types
EasyFXML - Native Support for platform-specific features (self-updates, native system notifications...)
EasyFXML - Samples Learn EasyFXML by example

Notes

This project makes heavy (and sometimes non-obvious) use of JavaFX and Spring Boot features, and requires knowledge of both for optimal experience. You can go head-first without that prior knowledge, but it might not be quite ideal is all.

Licensing and contributions

All contributions are welcome, both as questions, constructive criticism, feature requests and of course pull requests.

There is not yet a clear organization for making first-contributions easy, but a good rule of thumb is to ensure opening an issue before making a pull-request so that the technical implementation's requirements can be discussed before work is done. Then, crack on! :-)