Environment:
MacOS
IntelliJ Idea
Cucumber BDD Tests with Ruby
Execution of scenario from .feature file run into error with message "Error running Scenario No JDK specified"
Solved my issue
Go to IntelliJ Idea > Preferences
Go to Plugins
Click on 'Installed' tab
Search for 'Cucumber for Java' plugin
Unselect it to disable this plugin
Click on 'Apply' and then 'OK' button
Retry executing the same way as before (run scenario from .feature file)
Can anybody suggest better solution?
Related
I am having trouble updating my maven repositories in IntelliJ. I have three repositories that show errors, but IntelliJ doesn't show the full error messages.
I am looking in File >> Settings >> Build, Execution, Deployment >> Build Tools >> Maven >> Repositories
This is what I see:
I have tried the update button in the upper right, but I always get the "Error" message. What I can't figure out is where I can view what the actual errors are. Can anyone tell me where these error messages are logged or displayed?
I can build from the command line just fine. I am using the following:
Windows 10 Pro
IntelliJ Ultimate 2002.3.2
Maven 3.6.3
Java jdk1.8.0_66
If you have a stand-alone maven instance, and builds work fine from the command line, but they do not work from IntelliJ, it's likely that IJ is not configured to use the same maven settings as your system.
IntelliJ will use its bundled maven runtime rather than the one from your system. IJ will also use default maven settings locations.
You can modify these under the Settings > Build, Execution, Deployment > Build Tools > Maven screen. Make sure the settings match those in your systems MAVEN_HOME .
This information shows up in the idea log. This log can be found in the Help menu in the top search bar of the IntelliJ window.
Help >> Show log in explorer
You can then open and search the log using your preferred text editor.
https://intellij-support.jetbrains.com/hc/en-us/articles/207241085
#CrazyCoder provided this information in a comment.
My IntelliJ Idea projects have been working fine until I cloned a new project from our repo and installed Gradle.
This new project runs, but running the debugger causes the following error:
I've completed the steps recommended in this similar SO question. I have also read the Gradle Daemon guide.
Some helpful information:
-Gradle does respond to command line prompts, including --profile and --status:
-The project builds and executes; the problem is only the debugger. Is this a mapping issue between IntelliJ and Gradle?
-In the Settings menu, Gradle JVM: is set to "Use Project JDK (Java version "1.8.0_211") and this program is written in Java 8. Delegate settings set to: Build and run using intelliJ IDEA. Run tests using IntelliJ IDEA. Should these change to Gradle?
-I took the advice of one of the respondents and had one of our IT guys check out my ports and firewall settings. He was unable to solve the problem and said the issue is with Gradle.
So far, nothing has worked. What should I do?
I solved this problem after some tinkering:
In (IntelliJ) File > Settings > Build, Execution, Deployment > Gradle, I changed "Use gradle 'wrapper' task configuration" to "Use local gradle distribution."
Also, notice in this screenshot that "Gradle VM options" has a custom value; this was suggested as a solution in another post. This relates to memory management, as some people speculated that the daemon was crashing because of a RAM issue. My solution appears to work regardless of whether I alter that value.
I am using selenium maven project with Jenkins and when I run build now, execution is running in background for which I am able to see output in consol but my browser and all execution on browser is NOT visible.
I tried searching around and change Jenkins service by checking allow window interaction checkbox but still not able to view it. I m running on window 10 and running with local(http://localhost:8080). I tried with Chrome, firefox & IE and all have same behavior of Not visible.
I used command "mvn clean test" in Build - Execute Windows batch command.
Same project is running with Eclipse & CMD very well with visible execution.
I am using Jenkins version 2.46.3.
Anyone experienced this? Any idea ?
Run Jenkins or slave from command line using war or jar provided, other option to try: check 'Allow service to interact with desktop' in Services.
After lots of search & troubleshoot, I found solution as I installed Jenkins as Window version (.exe) so I uninstalled it and downloaded Jenkins from official jenkins website(https://jenkins.io/download/) by clicking on Generic Java Package(.war) and then went into Command prompt and went to path where my Jenkins.war file dowloaded and install using java -jar jenkins.war and reregister with different accountname and password (created new account so it won't pull up the old account) and the Execution started DISPLAYING ON BROWSER. Hope this helps.
I'm new to Gradle and while trying to install Gradle in my PC with Windows OS, I got the below mentioned error
Error: Could not find or load main class org.gradle.launcher.GradleMain
Only thing I did is that I followed the gradle installation steps given in gradle site Gradle installation and typed
gradle -v
in command prompt and I got the above mentioned exception. Any clue as to what had happened and how to resolve it.
This is what I have done :
Downloaded the zip file
Copied 'gradle-3.5' from the zip file to a folder I created in C drive (C:\Gradle)
Set GRADLE_HOME to 'C:\Gradle\gradle-3.5'
Set Path to '%GRADLE_HOME%\bin'
Opened cmd and typed gradle -v and got this error
I stopped all gradle daemons by running ./gradlew --stop and the error was resolved for me.
Basically this means that Gradle can't find your gradle/wrapper/gradle-wrapper.jar.
You have to follow Step 3 and setup environment variables:
Microsoft Windows users
In File Explorer right-click on the This PC (or Computer) icon, then
click Properties -> Advanced System Settings -> Environmental
Variables.
Under System Variables select Path, then click Edit. Add an entry for
C:\Gradle\gradle-3.5\bin. Click OK to save.
Source: https://gradle.org/install#configure
The easiest way, is to simply use gradlew.bat in your project and it will auto download Gradle for you!
I had the same issue after I removed the cache, the Gradle worker was running and I was getting this error
Error: Could not find or load main class worker.org.gradle.process.internal.worker.GradleWorkerMain
Steps I performed to resolve the error
Use gradle --stop or ./gradlew --stop
Delete the workerMain.lock file under $USER/.gradle/caches/version/workerMain
re-run the Gradle command
I'm using a Mocha Run/Debug configuration in WebStorm 11.0.3. I can see all my passing and failing tests in the panel at the bottom.
According to WebStorm documentation, I can "rerun the tests" or "stop and rerun the tests", but I don't see an option to only rerun tests that failed.
A Google search shows that "rerun failed tests" exists in PhpStorm and IntelliJ IDEA, two other JetBrains products. Perhaps they just left it out of WebStorm?
If it's not a built-in feature, is there a way to do this with mocha, perhaps by creating a report and reading the report on each run?
There is no 'Rerun Failed Tests' action available for Mocha. Would be a useful feature, please feel free to file a request for it to youtrack
In fact "ReRun Failed Tests" for Mocha tests is now available in WebStorm.
see https://www.jetbrains.com/help/webstorm/rerunning-tests.html