I usually only have to make one testclass that fullfills the needs of the testing

but you do give me an idea to look a the problem edvin and I were talking about

mocking a controller

I am not against mocking it has its place. in my line of work we usually only mock classes that we dont have full access too, like external libraries

this is an example of my kotlin + mockk + kluent test for spring boot:

class MyTest {
    val dependency: ConcreteDependency = mockk()
    val service = ServiceUnderTest(dependency)

    @Test
    fun `should test something`() {
        every { dependency.foo(any()) } returns "some result"

        val result = service.methodUnderTest("param")

        verify { dependency.bar() }
        result shouldEqual "some result"
    }
}

of

ConcreteDependency

was an interface it would work exactly the same except in my sources I would have to have duplicated signatures for

Dependency

and

DependencyImpl

I dont know mockk but I will look into that

mockito would look similar

so do you also mock database or rest service access that way

yes

ConcreteDependency

in this case would probably be a repository.. that way I can unit test without spinning up the db

in another case it is an

EmailService

since I dont want the test to send out email, I just use a mock and do no-op on

sendEmail(..)

methods

those are the things I usually use interfaces for

that code looks quite clean, I will certainly look more into this

yup MockK might be rough around edges but syntax-wise it's very clean

I'm not really familiar with build tools but I'll work on it tonight. fyi I'm a junior dev who's really struggling out here 😭

@Isaac maven is a good thing to learn because it's often used with different IDEs (NetBean, Eclipse, IntelliJ) and Continuous Integration (Jenkins, TravisCI)

I'll make sure to look it up. I had a nasty encounter with gradle the other time so I naturally decided to bin build tools in general

since gradle was making my life difficult

@ron when I'm done with the maven integration, I'll push it to the repo and I'll make sure to let you know about it. your thoughts are so important to me

@edvin can you open a PR with your thoughts? that way I know exactly what to focus on for now

@Isaac create a temporary new project with intellij and the tornadofx plugin, create a tornadofx maven project and use that as a template

man, I haven't used maven in years. been on gradle since android

I'm bumping into an issue testing my View with TestFX. It seems the Model it requests (

by inject()

) is being retained between tests. What's the best way to reset that?

@Carlton Whitehead uploaded a file: Untitled

Aha

@Carlton Whitehead uploaded a file: Untitled

Curious if this is actually a recommended approach. Feedback welcome

Does that just stop the process?

stop()

is a callback given by TestFX's ApplicationTest

and it does what?