Run the isolated tests in the web suite

Same defect as the uber suite, and the same fifty tests' worth of consequence.
execIsolatedTests is registered rather than being the task the java plugin
creates, so it had neither testClassesDirs nor classpath and was NO-SOURCE:
success, having run nothing. `test` excludes those same classes, so they ran
nowhere.

There is a third reason here, on top of the two the uber suite had. Nothing
declared this task as work: `build` runs `check`, `check` ran `test`, and
execIsolatedTests was reachable only by naming it. The shard plugin collects it
through tasks.withType(Test), which is why the joint workflow reached it at all
and gradle.yml never did. `check` now depends on it.

All fifty pass.

JSONBindingTests and AutoParams*MarshallingTests are dropped from the list.
1e38f1b deleted all three of those classes in June 2013 and added nothing:
the feature went, so the tests went with it, and naming them here selects
nothing and excludes nothing. Every other entry that matches no class in this
project is left alone, because those tests were moved rather than deleted --
GSPResponseWriterSpec and pages/ext/jsp to grails-gsp, GroovyPageAttributesTests
to grails-taglib -- and whether their successors still need isolating is a
question about those projects, not this list.

Author: jdaugherty

grails-test-report/build.gradle

@@ -35,6 +35,7 @@ def isolatedUnitTestPhases = [
         'isolatedRestRendererTests',
         'isolatedPersonTests',
         'isolatedRestfulControllerTests',
+        'execIsolatedTests',
 ]
 
 def reportVariants = [

grails-test-suite-web/build.gradle

@@ -60,8 +60,6 @@ def defaultTestConfig = {
 
 def isolatedTests = [
         '**/ContentFormatControllerTests.class',
-        '**/JSONBindingTests.class',
-        '**/AutoParams*MarshallingTests.class',
         '**/JSONBindingToNullTests.class',
         '**/ControllerWithXmlConvertersTests.class',
         '**/GroovyPageAttributesTests.class',
@@ -77,6 +75,11 @@ def isolatedTests = [
 
 tasks.register('execIsolatedTests', Test).configure { Test it ->
     it.configure(defaultTestConfig)
+    // A Test task registered rather than the one the java plugin creates has neither of these,
+    // which makes it NO-SOURCE: it reports success having run nothing. These classes are excluded
+    // from `test` below, so without this they run in no task at all.
+    it.testClassesDirs = sourceSets.test.output.classesDirs
+    it.classpath = sourceSets.test.runtimeClasspath
     it.forkEvery = 1
     it.includes.addAll(isolatedTests)
 }
@@ -95,6 +98,12 @@ tasks.named('test', Test).configure { Test it ->
     it.excludes.addAll(isolatedTests)
 }
 
+// Nothing else asked for this task, so `build` ran `test` and stopped. The shard plugin picks it
+// up through tasks.withType(Test), which is why the joint workflow reached it and gradle.yml did not.
+tasks.named('check') {
+    dependsOn('execIsolatedTests')
+}
+
 tasks.withType(Groovydoc).configureEach {
     // tests do not have groovydoc
     enabled = false