anyway thats exactly what I’m doing now, I’m guess...

# failgood

[christophsturm]

anyway thats exactly what I’m doing now, I’m guessing the file name, so you can now jump to tests and subcontexts from the test runner in idea. (in failfast main)

[dmcg]

#minutest resorts to creating an exception at the point where the test is defined and extracting the information from the stack trace

[christophsturm]

yes thats what i do too

[christophsturm]

i did it even before i worked on the junit runner because i output a stacktrace element that leads to the test.

[christophsturm]

in minutest, how do i select if i want to run tests with jupiter or with the minutest engine runner?

[christophsturm]

is a junit run config using the jupiter or the minutest engine?

[christophsturm]

ah i get it. it runs all tests for all engine

[christophsturm]

I was asking because i can’t jump to source code with the minutest engine, so i thought that it does not supply line number and file info

[dmcg]

Yes, I don’t know why that isn’t working. Rerunning a test isn’t either

[christophsturm]

things like this are hard to test because you cannot be sure what idea sends and how it reacts.

[christophsturm]

I don’t even know what i have to return to make idea show the option to rerun a single test.