JUnit runner page improvements

[labkey-tchad]

Rationale

For the most part, one is able to run individual server-side JUnit tests from junit-begin.view. This is not the case for parameterized test classes.

A minor change to how the page iterates through tests makes it function correctly for these tests.

Separately, the actions that actually run tests accepted GET requests, so a test run (some of which are expensive or have side effects) could be triggered by simply visiting a link.

Related Pull Requests

• N/A

Changes

• Fix the JUnit runner page to list every test method of a parameterized test class, instead of one opaque, unclickable entry per parameter set.
• Require POST for the actions that execute tests (RunAction, Run2Action, Run3Action); GoAction already required it.

[labkey-adam]

With this, we can probably adjust the mutating SQL detection, which currently ignores junit actions.

[labkey-tchad]

With this, we can probably adjust the mutating SQL detection, which currently ignores junit actions.

This was a bit trickier that expected. The mock ViewContexts used by some tests were tripping up the mutating SQL check. I had to tweak ViewContext.getMockViewContext to inherit the current view context.