The data engine fvt currently fails with it's property lookup.
This particular FVT makes use of a property file in it's maven implementation, and this issue is likely to do with the gradle classpath setup which needs correcting to ensure the file can be located
We need the FVTs to work under both maven and gradle (which we intent to ultimately migrate to).
opening up a separate issue
Note: ONCE FIXED, remove the exclusion from the test{} section in build.gradle to reenable the test
{"class":"VoidResponse","relatedHTTPCode":200}
=== Starting server: servergraph ===
200
{"class":"SuccessMessageResponse","relatedHTTPCode":200,"successMessage":"Fri Mar 12 10:23:22 GMT 2021 servergraph is running the following services: [Open Metadata Repository Services (OMRS), Connected Asset Services, Data Engine OMAS]"}
=== Configuration complete ===
:open-metadata-test:open-metadata-fvt:access-services-fvt:data-engine-fvt:configServer (Thread[Execution worker for ':' Thread 7,5,main]) completed. Took 18.518 secs.
:open-metadata-test:open-metadata-fvt:access-services-fvt:data-engine-fvt:test (Thread[Execution worker for ':' Thread 7,5,main]) started.
Gradle Test Executor 7 started executing tests.
Gradle Test Executor 7 finished executing tests.
> Task :open-metadata-test:open-metadata-fvt:access-services-fvt:data-engine-fvt:test FAILED
file or directory '/Users/jonesn/IdeaProjects/egeria.gradle/open-metadata-test/open-metadata-fvt/access-services-fvt/data-engine-fvt/build/classes/java/test', not found
Build cache key for task ':open-metadata-test:open-metadata-fvt:access-services-fvt:data-engine-fvt:test' is 47bd9eff72268a6bb245a763d266e557
Task ':open-metadata-test:open-metadata-fvt:access-services-fvt:data-engine-fvt:test' is not up-to-date because:
Task.upToDateWhen is false.
file or directory '/Users/jonesn/IdeaProjects/egeria.gradle/open-metadata-test/open-metadata-fvt/access-services-fvt/data-engine-fvt/build/classes/java/test', not found
Starting process 'Gradle Test Executor 7'. Working directory: /Users/jonesn/IdeaProjects/egeria.gradle/open-metadata-test/open-metadata-fvt/access-services-fvt/data-engine-fvt Command: /Library/Java/JavaVirtualMachines/zulu-15.jdk/Contents/Home/bin/java -Dfvt.url=https://localhost:9999 -Dorg.gradle.native=false @/private/var/folders/fb/mzlmglkd11g00z2wgc4m15nw0000gn/T/gradle-worker-classpath16955773089198063578txt -Xmx512m -Dfile.encoding=UTF-8 -Duser.country=GB -Duser.language=en -Duser.variant -ea worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Test Executor 7'
Successfully started process 'Gradle Test Executor 7'
DataEngineFVT > DataEngineFVT > initializationError FAILED
java.io.FileNotFoundException: /Users/jonesn/IdeaProjects/egeria.gradle/open-metadata-test/open-metadata-fvt/access-services-fvt/data-engine-fvt/build/classes/groovy/test/application.properties (No such file or directory)
at java.base/java.io.FileInputStream.open0(Native Method)
at java.base/java.io.FileInputStream.open(FileInputStream.java:211)
at java.base/java.io.FileInputStream.<init>(FileInputStream.java:153)
at java.base/java.io.FileInputStream.<init>(FileInputStream.java:108)
at org.odpi.openmetadata.accessservices.dataengine.PlatformConnectionProvider.getConnectionDetails(PlatformConnectionProvider.java:48)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.
4098 adds FVT support to the gradle build.
The data engine fvt currently fails with it's property lookup.
This particular FVT makes use of a property file in it's maven implementation, and this issue is likely to do with the gradle classpath setup which needs correcting to ensure the file can be located
We need the FVTs to work under both maven and gradle (which we intent to ultimately migrate to).
opening up a separate issue
Note: ONCE FIXED, remove the exclusion from the test{} section in build.gradle to reenable the test