testCoverage: TestCoverage,
        parallelization: (Int) -> ParallelizationMethod,
    ): List<SmallSubprojectBucket> {
        // splitIntoBuckets() method expects us to split large element into N elements,
        // but we want to have a single bucket with N batches.
        // As a workaround, we repeat the bucket N times, and deduplicate the result at the end

        Pattern pattern = Pattern.compile(wrongPattern);

        // Without escaping, "application/xhtml+xml" does NOT match
        // because the pattern expects "one or more 'l'" followed by "xml"
        assertFalse(pattern.matcher("application/xhtml+xml").matches());
        assertFalse(pattern.matcher("application/rdf+xml").matches());
    }

    @Test

{HTMLElement} data.arrowElement Node used as arrow by arrow modifier\n * @property {Object} data.styles Any CSS property defined here will be applied to the popper. It expects the JavaScript nomenclature (eg. `marginBottom`)\n * @property {Object} data.arrowStyles Any CSS property defined here will be applied to the popper arrow. It expects the JavaScript nomenclature (eg. `marginBottom`)\n * @property {Object} data.boundaries Offsets of the popper boundaries\n * @property {Object} data.offsets The measurements...

import spock.lang.Specification

class PreparePatchReleaseTest extends Specification {

    def "patch version is correctly bumped"() {
        expect:
        ReleasedVersionsHelperKt.bumpPatchVersion(input) == expected

        where:
        input   | expected
        "9.4.0" | "9.4.1"
        "9.4.1" | "9.4.2"
        "8.0.0" | "8.0.1"
        "1.2.3" | "1.2.4"
    }

                return webApiManager;
            }
        };
        ComponentUtil.register(factory, "webApiManagerFactory");

        // Execute and expect IOException
        try {
            webApiFilter.doFilter(request, response, chain);
            fail("Expected IOException");
        } catch (IOException e) {
            assertEquals("Test IOException", e.getMessage());
        } catch (ServletException e) {

        // OutOfMemoryError is an Error, not Exception, so it will not be caught
        // The test should expect the error to propagate
        try {
            purgeDocJob.execute();
            fail("Expected OutOfMemoryError to be thrown");
        } catch (OutOfMemoryError e) {
            assertEquals("Out of memory", e.getMessage());
        }
    }

    @Test

        def projectDir = 'C:\\some\\agent\\workspace'

        expect:
        (line =~ KillLeakingJavaProcesses.generateLeakingProcessKillPattern(projectDir)).find()
    }

    def "matches daemon process started by performance test on Windows"() {

        String value;
        String expect;

        value = null;
        expect = "";
        assertEquals(expect, ParameterUtil.encrypt(value));

        value = "";
        expect = "";
        assertEquals(expect, ParameterUtil.encrypt(value));

        value = "\n";
        expect = "";
        assertEquals(expect, ParameterUtil.encrypt(value));

        value = "=";

        def snapshot = snapshot('4.3')
        def rc = releasedVersion('4.3-rc-1')
        def versions = releasedVersions(snapshot, rc, [])
        def version = new ReleasedVersion('4.2', '20170913122310+0000')

        expect:
        ReleasedVersionsHelperKt.updateReleasedVersions(version, versions) == releasedVersions(snapshot, rc, [version])
    }

    def "final releases are sorted by version"() {
        def snapshot = snapshot('4.3')

Symmetrically, the same problem exists on the side of Gradle maintainers.
It should be clear when introducing a property what contract users can expect and what we can afford to provide.
As features progress through the lifecycle of stabilization and, possibly later, deprecation, the corresponding properties can also adjust accordingly.