Robotium Error message - automation

After click on the New test for robotium recoder I am getting error message for Please select the root Java JDK folder.
My JAVA_PATH,HOME_PATH,CLASSPATH are saved properly in the environmetn variables.
I am using windows 10.(64-bit)Screenshot for issue

You wrote about
JAVA_PATH,HOME_PATH,CLASSPATH
Is %JAVA_HOME% configured correctly?
You can simply verify it using cmd.exe
java -version
If yes - add JDK for eclipse.
This article should help:
How to Change JDK version for an eclipse project
UPD:
Here steps for Robotion with screenshots with your issue resolved:
Blog

Related

IntelliJ error - could not open init generic class cache for initialization script

enter image description here
enter image description here
I was trying to download IntelliJ and learn Kotlin, but i get a BUG error before i am starting, and i dont now what to do..
I have try to delete the scipts folder, but it just make a new scipts folder, and say the same error. I have also reinstall IntelliJ, and thats give the same error.
Is der someone there can help me? :-)
Could not open init generic class cache for initialization script 'C:\Users\username\AppData\Local\Temp\wrapper_init4.gradle' (C:\Users\username.gradle\caches\6.6.1\scripts\3yb5naxddghzghazzdf2vk0em).
BUG! exception in phase 'semantic analysis' in source unit 'BuildScript' Unsupported class file major version 60
As per the details in your error message, you can see that the root cause is a gradle error.
Gradle is likely using an unsupported version of the JVM in your case (e.g. I could reproduce the error in the latest IntelliJ 2021.3 version where gradle was using JVM 17 from my home path, while the IDE itself was using JDK 11.) In the attached IntelliJ Preferences screen, note that the JVM used by Gradle is specified separately.
To fix the error, verify the JVM version being used by gradle and specify a JVM 11 version to gradle.
IntelliJ Gradle Preferences Screenshot:
You should set these options when you create your project enter image description here
Or, when creating a project, choose Java - Kotlin\JVM
For me this problem occurred when i was using wrong JDK file to build the project that is the Gradle JDK used was a normal SE JDK rather than one preferred by Android Studio so you follow the following steps to solve it.
Go to Settings (ctrl + alt + s)
Go to Build,Execution and Deployment
Then select Build Tools > Gradle
Change Gradle JDK to jbr-17 (the one i am using) you can prefer to choose options from Android studio Java Home or Default JDK

intellij won't start after switch boot jdk

I wanted to debug my project under Open JDK 11, so I tried to switch boot jdk to the OpenJDK11 path. I am using the community version on Windows 10.
The suggested restart didn't happen, I only got the following error:
JDK needed
How can I reset the boot jdk without Intellij starting?
Thanks in advance and kind regards
The IntelliJ Advanced Configuration docs say the configuration directory on windows is:
Syntax
%HOMEPATH%\.<product><version>\config
Example
C:\Users\JohnS\.IntelliJIdea2019.3\config
Then, just delete the studio.jdk file in that directory, and IntelliJ will boot with its default.
I have a related answer about Android Studio
For MacOS(checked on Catalina) just run the "repair" binary located in:
/Applications/IntelliJ IDEA CE.app/Contents/bin
you can just delete this config file /Users/xxx/Library/Application Support/JetBrains/IntelliJIdea2022.1/idea.jdk

How to debug an IntelliJ plugin in a different platform (eg. Pycharm)

I have a license for PyCharm Professional and am using IntelliJ IDEA Community Edition to develop a plugin for it. I need to run the plugin in PyCharm to test it out. I can't use the Python plugin for IntelliJ IDEA to test it as only the Community edition of the plugin appears to be available for me. If I manually download the professional version and try to install it I get Plugin 'Python' is incompatible with this installation. I assume I would need IntelliJ IDEA Ultimate to be able to use the professional version of the Python plugin.
I saw this question, which suggests it is possible to use PyCharm as the target for a "Plugin" run configuration, but I haven't had any luck following those steps. I set the JRE to /opt/pycharm-professional/jre64 but got Exception in thread "main" java.lang.ClassNotFoundException: com.intellij.idea.Main. I then grabbed the java command line args from a running instance of PyCharm and added those in (particularly the classpath) but got Error: Could not find or load main class com.intellij.rt.execution.application.AppMainV2. I haven't been able to find anything in the docs on how to set this up.

IntelliJ IDEA 14.03 failed to browse JDK 1.8 source code

I added the latest JDK 1.8 into my projects in IntelliJ IDEA 14.03. But later I found that I can't jump to the source code of any class from JDK. IntelliJ always using the internal java decompiler showing the source code decompiled from .class, even I manually disable the decompiler plugin!
When I switch back to Oracle JDK 1.7, everyting is fine.
Anyone has the same issue?
I am using MacOS 10.10.2(Yosemite)
I found the anwser. After "Invalid cache and restart", everything is working again.

IBM Worklight v6.0 - Error while adding an application to the Mobile Test Workbench

I have a Worklight app, created an apk file from it. Created a Test Project.
Adding the apk file to the workbench, it has an error saying:
Application xxx.apk cannot be imported; it is either an invalid one or
it contains specific features that are not supported.
Try opening the .log file for the worklight workspace. I saw an error saying that for the Rational Test Workbench to work, I need to use JDK and not JRE.
The solution that solves my problem is as follow:
In the workspace, go to Window > Preferences
Expand Java > Installed JREs
Add a new JDK and ticky mark it
Open the xxx.ma file
You should still see the error in that file
Select the mobile app from the test workbench file. Delete it
Add the mobile app again to the test workbench file. It will take some time to process.
The problem is most likely to do with the fact that your Eclipse is not pointing to a JDK.
Please edit eclipse.ini to point to your JDK (-vm ... jdk location...)