Open timothyklim opened 3 months ago
Which munit version are you using?
Could you verify if this is still the case with 1.0.0-RC1, please.
Which munit version are you using?
Could you verify if this is still the case with 1.0.0-RC1, please.
I'm using 1.0.0-RC1.
As a workaround you can use -F option for running. In sbt added after -- for example:
sbt project/testOnly MySuite -- -F
Otherwise, looks like a but. But I don't think it's blocking 1.0.0.
As a workaround you can use -F option for running. In sbt added after -- for example:
sbt project/testOnly MySuite -- -F
Otherwise, looks like a but. But I don't think it's blocking 1.0.0.
I'm using bazel and want to understand what I need to do inside test runner please. Found in ./docs/troubleshooting.md
As a workaround you can use -F option for running. In sbt added after -- for example:
sbt project/testOnly MySuite -- -F
Otherwise, looks like a but. But I don't think it's blocking 1.0.0.
With -F
the same result on 1.0.0 release.
For
assert
I get full stack trace likebut for assertEquals I need to debug all asserts in all helpers because stack trace is a single line: