Gradle resource are copied to resource/test not classes/test

[peterquiel]

The following configuration form the documentation ensures, that resource files in source directory are respected

sourceSets {
    test {
        resources {
            srcDir file('src/test/java')
            exclude '**/*.java'
        }
    }
}

With this configuration the resource files are copied to build/resource/test folder where they are not picked every relative to class method.

Changing the resource output directory to build/classes/java/test solves this problem.

sourceSets {
    test {
        output.resourcesDir = "build/classes/java/test"
   }
}

I personally find it surprising that the com.intuit.karate.Runner#runFeature(java.lang.Class, java.lang.String, java.util.Map<java.lang.String,java.lang.Object>, boolean)
and com.intuit.karate.Runner#runFeature(java.lang.String, java.util.Map<java.lang.String,java.lang.Object>, boolean) behaves different.

[ptrthomas]

sounds like a gradle thing, marking this ticket as "help wanted" as we use maven

[peterquiel]

Could it be an option for you to create a fallback in the 'relative feature file resolving' method?

Something like: If don't find the feature file next to the class file, I will try to create a class path lookup for the feature like its done in all the classpath:com.x.y.karate.feature lookup methods.

Happy to create a PR...

[ptrthomas]

I don't remember the details - but that routine has been through a few iterations to get resources within JAR files to work #520

not able to follow what you mean about the "behaves different", maybe you can add a test here: https://github.com/intuit/karate/blob/master/karate-core/src/test/java/com/intuit/karate/RunnerTest.java - and yes a PR sounds good

[peterquiel]

I created a PR #739 to fix the gradle build in karate-demo.
I will have a deeper look into the FileUtils/Resource lookup stuff in order to explain the problem in detail.

[peterquiel]

I created a Test in my personal repository because it's tricky to reproduce the behavior with maven.

I hope this test explains the problem:
https://github.com/peterquiel/karate-experiment/blob/master/src/test/groovy/com/github/peterquiel/karate/experiment/CallFeatureFromJavaTest.groovy#L25

Here is a naive solution to the problem:
develop...peterquiel:experiment-to-solve-relative-resource-loading-with-gradle

[ptrthomas]

@peterquiel it looks ok to me, you can go ahead with a PR if it doesn't break any existing tests.

[peterquiel]

Done: #764

[ptrthomas]

released 0.9.3