@edvin yeah, I think this is a great separation (guide/wiki), too.

I will switch my focus to transferring all the stuff from the wiki to the guide and then wipe the wiki and set it up for the cookbook 🙂

regarding the SO question.

I am testing a View() and not an App(). If I use MyMainApp().start(stage) and then MyMainApp().stop(), I get the required behaviour.

But how to do this for Views and Fragments. so, some software test people wrote about various properties/qualities of tests. kent beck for instance says, among other points, tests need to be isolated. a similar quality is, that they should be repeatable.

these two qualities are also listed in the pragmatic unit testing book by andy hunt and dave thomas

A view can be created as a unique instance by

find<ViewType>(Scope())

and for Fragment you'd always get a new instance with

find<FragmentType>()

.

we usually use

@Before

and

@After

(I call them test lifecycle methods/annotations) to prepare and clean the tests, i.e. to have this isolated property.

You could set a new scope in

@Before

and then

find

all resources for the current test in that scope perhaps?

now there is the problem with cleaning the whole stage up, or only replacing the scene within the stage (when we think about JavaFX). and the problem with the singleton `View`s, which need to be instanciated with

find<...>(...)

(when we think about TornadoFX)

(Set, meaning putting the scope for the test in a variable accessible to the test)

Is it a problem to use

find

?

no, not at all. but we need to tell the test writer somehow, or better, provide something like

ViewTestBase

class.

there are so many different use-cases, just for the setup of test fixtures... you can setup independent nodes, scenes with nodes in it, whole stages, applications (and `App`s), and we also need to support `View`s, `Fragment`s...

TestFX 3 only supported setup of `Stage`s. this meant, we couldn't write internal tests, that don't need `Stage`s.

I need to look into the source code of

Scope

OK, I see. So a testfx-tornadofx test dependency is probably the best way to go, right? Scopes are pretty easy to reason about, let me know if you have any questions. And thanks for looking into this, Benjamin. I think it would help our credibility a lot to be able to provide a standard way to test TornadoFX UIs.

there are scope tests 😄 https://github.com/edvin/tornadofx/blob/master/src/test/kotlin/tornadofx/tests/ScopeTests.kt

Totally random question guys. I'm having a double-take because I'm encountering people styling Java code like this:

@User uploaded a file: Untitled

When it comes to Java style, a curly bracket should always go at the end of the line where the declaration takes place right? I'm correcting several people who are doing this, and I'm wondering if maybe I'm being a style nazi

C# programmer?

That's what I'm thinking

even the code under the

package

"block" is indented

I know...

like a C# `namespace`: https://msdn.microsoft.com/en-us/library/z2kcy19k.aspx

Ah, okay. Now this makes sense why are doing it.

I'm writing a book with Packt right now and one editor going through and editing my code this way

So it's not just me, thank you @hastebrot!

People I've encountered at work are doing it this way too.

@thomasnield Several Java-people have been doing this as well, and for years, even before C# was created.

@thomasnield You'll find large open source Java projects with this indentation style.