I have a eclipse plugin project which runs by opening eclipse UI. I have added an extension
org.eclipse.core.runtime.applications
to run that plugin headless for some testing purpose. Now if I run that plugin project from context menu run option. It always run project in headless mode until i do not choose UI launch configuration by opening run configuration window.
Any idea how we can set default launch configuration to run it via opening UI? so i do not need to select launch configuration every time through run configuration window. Same problem is there in case of debug.
Related
always before launching my app I'm running all the unit tests to make sure there is no regression. So I have two separate tasks and run all tests, and then I launch the app.
I'm curious if there is any option of setting the configuration this way that I click "Run" button, and it invokes build, tests and launch?
Thanks!
IntelliJ IDEA provides Compound Run/Debug configurations exactly for that:
Use this dialog box to create configurations containing multiple run/debug configurations that you can launch at once. This is useful, for example, if you want to launch various automated tests and get test results in one window.
I'm developing an intellij plugin supposed to be used in android studio.
I've already setup the plugin development environment, but when I hit "Run" command it starts a new intellij instance with the plugin installed.
What I'm looking for is how to run the plugin directly on Android Studio, is that possibile? The only place where I think it can be configured is from "Run configurations" but I do not find anything useful there.
Thanks
You can specify the platform to run on in the IntelliJ Platform Plugin SDK settings, under Platform Settings | SDKs in the Project Structure settings. Point the IntelliJ Platform Plugin SDK home path to your Android Studio installation.
Another option is to create a new Plugin Run Configuration. In the Run Configuration it is possible to specify the JRE to run on. Click on the ... button there and select an Android Studio installation directory (e.g. /Applications/Android Studio.app/Contents on the Mac). This way it is possible to create a Run Configuration for all IntelliJ Platform IDEs you want to test your plugin on.
We're using IntelliJ version 14 and are trying to add Jacoco code coverage to our remote Java application project. This is defined under the "Remote" option in the Edit Run/Debug Configuration.
Is there any way to activate Code Coverage for Remote app? There is no "Coverage" tab.
This is not a standard app with a main method.
Thanks
Enabling code coverage requires adding a JVM agent that instruments bytecode to collect coverage information. When you use the Remote configuration, the JVM is not started by IntelliJ IDEA, and therefore there is no way to enable code coverage through the IntelliJ IDEA UI.
You can enable the coverage manually by modifying the VM options used to start your remote process and adding the coverage agent.
I am unable to run or debug any TestNG tests in IntelliJ 13.1.4 on my Mac. When I try to run the test in debug mode, the IDE is hung starting the test - it never completes.
However, I can work with the same test using an older version of IntelliJ (12.1.7).
So far I've tried changing the JDK, replacing the testng jar in ../IntelliJ13/plugins/testng/lib, reimporting all maven dependencies, rebuilding IntelliJ indices.
Any ideas about how to fix my IntelliJ 13.1.4 environment?
I had similar issue - it turns out that I need to config my JVM options and connection used.
Update:
Sadly no, they are internal resources. But the algorithm should be the same (for your case):
goto Run/Debug Configuration
select TestNG
add your Name for the new configuration
select path to your test suite in Suite
in JDK settings tab, find VM options input your connection configs
run/debug for the Run/Debug Configuration - menu arrows
this worked for me.
Ok, I'm using Ember-App-Kit which uses Testem/Qunit, but I can't figure out how to debug tests, especially since either Testem or Qunit close the QUnit tests window so I can't set any breakpoints, and node debug with debugger doesn't work since it's in browser.
I tried to set the debug: true property in grunt-contrib-testem but that didn't do anything..
So if anyone can help, that would be awesome. I'm using the default EAK setup without any changes.
You'll need to do a few things:
Keep the grunt server task running in one window -- this will rebuild your test assets and compile them into the build/test directory.
Run Testem in standalone mode -- you'll first have to install testem via npm (npm install -g testem) then call testem from your app's root directory. Alternatively, you can run grunt test:server, which will let you run testem without installing globally.
Drop a debugger statement in your test body. In an open Chrome window running the Testem harness, open your Developer Tools console window.
Refresh the Chrome window, and you'll now have breakpoint capabilities in your tests.