Add contextSize test parameter to enlarge the scope of a diff

[TonioGela]

As per description, this PR introduces a contextSize overridable suite parameter that control the number of lines around the reported diff in case of a mismatch ( ala grep -A <n> -B <n>)

Ofc the normal behaviour was kept identical to the actual, and there's no change in the user API (at least for the methods used via Assertions)

[TonioGela]

Hmm, given that a lot of the stuff in Diff is effectively exposed the mima check screams with 11 compatibility errors. I'll try to figure out a better encoding for the content of this PR, so don't take it too seriously for the moment 😇

[tgodzik]

Shouldn't this be a parameter to the runner

munit/munit/js-native/src/main/scala/munit/internal/junitinterface/JUnitFramework.scala

Line 110 in 8b63f0e

case "-F" => trimStackTraces = false

?

[TonioGela]

Shouldn't this be a parameter to the runner

munit/munit/js-native/src/main/scala/munit/internal/junitinterface/JUnitFramework.scala

Line 110 in 8b63f0e

case "-F" => trimStackTraces = false

?

Interesting question. Going further: should it just be a parameter or also a parameter?

[tgodzik]

I think just a parameter since it doesn't really change the test logic, but how the test is being displayed. Potentially we could have runner defaults for a specific suite as a separate thing.

[tgodzik]

btw. MiMa is not a huge issue here, we would need to do 1.1.x next so that it's automatically picked up as possible incompatibility

[TonioGela]

I think just a parameter since it doesn't really change the test logic, but how the test is being displayed. Potentially we could have runner defaults for a specific suite as a separate thing.

Okay, this seems reasonable. I'll try to rework it. I'll also try to add documentation about that flag maybe here: https://scalameta.org/munit/docs/troubleshooting.html