coroutines might be a perfect case for this...they seem to mix synchronous and asynchronous statements in a more intuitive manner

I don't think a complete reactive approach will work for you because you'd have to put all your test results reporting in onFail or onFinished blocks

@carlw @alexp11223 if you use a TestObserver or TestSubscriber in RxJava, you can easily package that up in a test.

But only use Rx if you need to asynchronously carry an event through several steps and operations that you fluently want to compose. Otherwise, yes coroutines may be simpler

@thomasnield I think the Phaser/CountdownLatch is going to be the best approach because it will let you eventually work with a Runner like JUnit and report back the results after a test

Man, I havent used Phasers, CountDownLatch, Semaphores, and all those utilities in a long time. I do use Atomic types though.

I think the core of the decision on which to use depends on how reactive the codebase is already. If it is not reactive or only some parts of it are, by all means dont bloat up with that dependency. Otherwise it is helpful to get to know the Rx tools to bridge reactive and nonreactive worlds.

i pick my battles with unit testing and fx. i wrote model and client-side business logic (view logic) components as plain as possible so that they can be tested

i was looking at a different strategy to test async operations, properties, etc using a tool called Test Complete which manipulates the FX controls as Java objects like the layout debugger or scenic view

i put a few JavaFX unit tests in a project a while back, but they actually became a maintenance drag and didn't improve the quality of the code

Test Complete looks great. there's a learning curve though https://smartbear.com/product/testcomplete/overview/

how to autoscroll textarea to bottom? I tried this but no effect

outputArea = textarea(viewModel.outputProperty) {
                        isEditable = false
                        textProperty().onChange {
                            outputArea.scrollTop = Double.MAX_VALUE
                        }
                    }

as well as

appendText("")

and

selectPositionCaret(length)
deselect()

@alexp11223 you're looking for end()

@User uploaded a file: Untitled

Nice, I did't know about that one. So

textProperty().onChange { end() }

would work?

I think it would break if you edit anywhere but at the end of the document though.

yeah my example isn't scrolling as you go along

but sometimes with scrolling you have a deliberate UI control like a checkbox that puts the user in the end of file mode

like glogg or baretail

that can be turned off if you want to edit elsewhere

textProperty().onChange {
                            end()
                        }

doesn't work too

that would move the cursor anyway.

are you trying to keep the cursor at the end of the textarea?

I don't care about cursor, it's readonly, like log

@alexp11223 You wrote

isEditable = false

?

yes

So how chan it change?

Your viewmodel outputproperty changes?

yes