使用Spock框架做API自动化（Java Groovy）运行用例后遇文件找不到错误

Hey there, let's break down what's going on with your Spock API tests—those FileNotFoundException errors and "Test Ignored" messages are definitely linked, so let's tackle them together.

Why the FileNotFoundException pops up #

First, that error is telling you the test can't find your CitiesData.csv file, and there are a few common reasons for this:

• Hardcoded absolute path: The path in your error (C:**LOCAL PATH**\src\test\resources\CitiesData.csv) is a local absolute path. This works only on your machine—if you run tests in a different environment (like CI) or even if your IDE's working directory isn't your project root, it'll fail. Never hardcode absolute paths for test resources.
• Incorrect resource loading method: If you're using new File("src/test/resources/CitiesData.csv"), this looks for the file relative to the current working directory. But when tests run via build tools (Maven/Gradle) or IDE test runners, the working directory might not be your project root. Instead, you should load resources from the classpath, which is the standard way to access test resources.
• File not in the right place (or misnamed): Double-check that CitiesData.csv is actually in src/test/resources (not a subfolder unless you adjust your path), and that the filename matches exactly (case matters on Linux/macOS, even if Windows ignores it). Also, make sure it's not excluded by .gitignore or your build tool's resource filters.

Why tests are being "Ignored" #

The ignored tests are almost certainly a side effect of the missing file:

• Test setup failure: If your test tries to load the CSV in a setup() method or during test initialization, the uncaught FileNotFoundException might cause Spock to skip the test instead of marking it as failed (some IDEs or test runners handle initialization errors this way).
• Conditional ignore annotations: Check if you're using @IgnoreIf or similar Spock annotations that skip tests when the file isn't found. If your condition checks for the file's existence and it's missing, the test gets ignored.
• Explicit @Ignore annotations: It's worth double-checking that you didn't accidentally add @Ignore to test classes/methods without realizing it.

Fixes to try right now #

Let's get this sorted with actionable steps:

1. Load resources from the classpath (the right way)
   Replace your file loading code with classpath-based loading—this works regardless of where tests are run:

   // Option 1: Get a File object (if you need it)
   def csvResource = getClass().getResource("/CitiesData.csv")
   if (!csvResource) {
       throw new IllegalStateException("CitiesData.csv not found in test classpath!")
   }
   def csvFile = new File(csvResource.toURI())
   
   // Option 2: Use an InputStream (better for most cases, avoids File issues)
   def csvInputStream = getClass().getResourceAsStream("/CitiesData.csv")
   if (!csvInputStream) {
       throw new IllegalStateException("CitiesData.csv not found in test classpath!")
   }
   

   If the file is in a subfolder (e.g., src/test/resources/data/CitiesData.csv), adjust the path to /data/CitiesData.csv.

2. Verify your resource setup

   • Confirm CitiesData.csv is in src/test/resources
   • Check for typos in the filename (e.g., citiesdata.csv vs CitiesData.csv)
   • For Maven/Gradle: Ensure your build tool is copying test resources to the classpath. Both tools do this by default, but if you've customized testResources (Maven) or sourceSets.test.resources (Gradle), double-check those configurations.

3. Debug ignored tests
   Look at the full test logs (not just the summary) to see exactly why tests are being ignored. The stack trace from the FileNotFoundException should show up in the logs, confirming that the missing file is the root cause.

4. Ditch absolute paths entirely
   Remove any hardcoded absolute paths from your test code—classpath-based loading is the reliable, portable way to access test resources.

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