Right now, TestComplete only builds a JavaBridge based upon the JRE. The JDK includes the JRE so all you need to do is indicate the directory where the JVM files are.
Note that the JRE option in TestComplete is ONLY necessary if you want to utilize Java classes as part of your test cases (such as I do with the PDFBox application). If your application is built in Java, there's no need to specify the JRE.
HOWEVER... that said, currently TestComplete only supports testing Desktop applications built with certain Java technologies (https://support.smartbear.com/testcomplete/docs/app-testing/desktop/java/about.html#supported-java-technologies). If your application is built with a different technology, it doesn't necessarily mean you can't use TestComplete, just that some of the Open application feature set is not supported.
If you need JRE/JDK 11 support, I'd suggest you contact your Customer Success Manager at SmartBear and inquire as to when support will be made available in TestComplete.
Thank you for your response.
I have updated the Hava Bridge to point to our open JDK 11.0.1 jvm.dll file, but TC still attempts to use my JRE 8 VM. Is there another location for me to specify the JDK directory?
Keep in mind, that setting is stored per machine per user. So, if you are running something using a different user or on a different machine, you need to make that setting change there as well.
That is the ONLY place to indicate the JVM to use by TestComplete for JavaBridge work.
Even though I have set up the JavaBridge to point to the jdk 11's jvm, the tested application still only shows jre1.8.0 as the only VM to choose.
OF course.. because you're selecting the JavaW.exe from the 1.8 folder. You need to change the actual tested application to point to the new JavaW.exe for the JDK 11. JavaBridge has nothing to do with that..
REad up on JavaBridge (https://support.smartbear.com/testcomplete/docs/testing-with/advanced/using-external-functions/calling-from-java-classes.html). The JavaBridge is for calling Java classes within your script code.
Again, I reference to something I mentioned above. TestComplete 12.60 only supports Java applications up through version 10. So, the possible problem you're dealing with is that it's not recognizing the JVM for the JDK 11.
