如何在未安装Groovy的服务器上运行含Spock测试的Jar包

Alright, let's figure out how to run your Spock test JAR on a server without Groovy or Spock pre-installed. Here's what you need to do step by step:

1. Ensure You Have a Fat (Uber) JAR #

The biggest requirement here is that your test JAR must include all dependencies (Groovy, Spock, JDBC drivers, etc.) and your test classes themselves. A regular JAR won't work because the server doesn't have those libraries available.

If You're Using Gradle #

Use the Shadow plugin to build a fat JAR that includes test code and dependencies. Add this to your build.gradle:

plugins {
    id 'groovy'
    id 'com.github.johnrengelman.shadow' version '8.1.1'
}

dependencies {
    testImplementation 'org.spockframework:spock-core:2.3-groovy-4.0'
    // Add any other test dependencies (like JDBC drivers) here
}

shadowJar {
    // Include test classes and test runtime dependencies
    from sourceSets.test.output
    configurations = [project.configurations.testRuntimeClasspath]
    mergeServiceFiles() // Required to handle service loader entries for Spock/JUnit
}

Run ./gradlew shadowJar to build the fat JAR (it'll be in build/libs/ with a -all suffix by default).

If You're Using Maven #

Use the Maven Shade plugin to package a fat JAR with test code:

<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-shade-plugin</artifactId>
            <version>3.5.1</version>
            <executions>
                <execution>
                    <phase>package</phase>
                    <goals>
                        <goal>shade</goal>
                    </goals>
                    <configuration>
                        <includes>
                            <!-- Include your test classes -->
                            <include>com/yourpackage/**/*Spec.class</include>
                        </includes>
                        <transformers>
                            <transformer implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/>
                        </transformers>
                    </configuration>
                </execution>
            </executions>
        </plugin>
        <!-- Make sure test classes are compiled and included -->
        <plugin>
            <groupId>org.codehaus.mojo</groupId>
            <artifactId>build-helper-maven-plugin</artifactId>
            <version>3.4.0</version>
            <executions>
                <execution>
                    <phase>package</phase>
                    <goals>
                        <goal>add-test-resources</goal>
                    </goals>
                </execution>
            </executions>
        </plugin>
    </plugins>
</build>

Run mvn package to generate the fat JAR.

2. Run the Test JAR on the Server #

Once you've uploaded the fat JAR to the server, use these commands to execute your tests:

Run an Entire Test Class #

If you know the full qualified name of your Spock spec class (e.g., com.yourpackage.DatabaseSpec), use either JUnit or Spock's runtime runner:

# Using JUnit Core (Spock is compatible with JUnit)
java -cp your-test-fat.jar org.junit.runner.JUnitCore com.yourpackage.DatabaseSpec

# Using Spock's own runner (more feature-rich for Spock-specific options)
java -cp your-test-fat.jar org.spockframework.runtime.SpockMain com.yourpackage.DatabaseSpec

Run a Single Test Feature (Your "connect via jdbc" Test) #

From your decompiled code, you see the feature name is "connect via jdbc". Spock's runner lets you target specific features with the --include flag:

java -cp your-test-fat.jar org.spockframework.runtime.SpockMain --include "connect via jdbc" com.yourpackage.DatabaseSpec

Make sure to wrap the feature name in quotes to handle spaces correctly.

3. Key Notes #

• Java Environment: The server only needs a compatible JRE (Spock 2.x requires Java 8+; check your Spock version's requirements).
• Verify the Fat JAR: You can inspect the JAR with jar tf your-test-fat.jar to confirm it contains groovy-all-*.jar, spock-core-*.jar, and your test .class files.
• Feature Names: If the --include flag doesn't work, double-check the exact feature name from decompilation (case-sensitive, including spaces/punctuation).

内容的提问来源于stack exchange，提问作者Loom