You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In https://gradle.github.io/playframework/#project_layout, it describes a /test folder to hold test files. But didn't mention about test sources files and test resources files.
Is there a convention for test resources files?
I see some play apps are having /test/ folder to contain test sources files and /test/resources to contain test resources files, I am wondering if this is a good approach and if it is following gradle play best practice convention.
In my understanding a normal approach is to have different dedicated folder for test sources files and test resources files, e.g. /test/java for test sources files and /test/resources/ for test resources files.
The text was updated successfully, but these errors were encountered:
We came across this as well when migrating from sbt to gradle.
In sbt, test/resources is reserved for testing resources, however during migration we found that our test resources weren't being picked up while running tests. According to running
sourceSets.test {
println(resources.srcDirs)
}
we see that by default the test resources directory is set to src/test/resources.
In https://gradle.github.io/playframework/#project_layout, it describes a /test folder to hold test files. But didn't mention about test sources files and test resources files.
Is there a convention for test resources files?
I see some play apps are having /test/ folder to contain test sources files and /test/resources to contain test resources files, I am wondering if this is a good approach and if it is following gradle play best practice convention.
In my understanding a normal approach is to have different dedicated folder for test sources files and test resources files, e.g. /test/java for test sources files and /test/resources/ for test resources files.
The text was updated successfully, but these errors were encountered: