Not able to remote debug tests in Intellij when executing tests using gradle test task












0















I have a spring boot project (Java 8, JUnit 4). I am using IntelliJ for IDE. My test passes when I run from within IntelliJ but fails when I run it from command line using gradle test command. So I am trying to remote debug my Junit test. I have breakpoints set. But when the test is executing the debugger is not stopping at the breakpoints. This is what I have done so far:




  1. I have created a remote debug configuration in IntelliJ with port as 5005

  2. I am running this command: gradle test -Dtest.debug on command line

  3. I see build output that the build is waiting for the debugger to connect to port 5005 and the process suspends

  4. At this point I run my remote debug configuration and it successfully connects to port 5005

  5. After this the JUnit test is executed but the debugger does not stop at the breakpoints.


In fact when the test is running the breakpoints on the junit test are changing to lite gray color. This tells me that the JVM IntelliJ debugger got connected to did not have the executable code for my test. Gradle is spinning off multiple JVMs I believe and IntelliJ is connecting to the wrong one. How can I validate this?



How to make debugger stop at the breakpoints? Really appreciate someone's help.










share|improve this question

























  • Not sure if it'll make a difference, but what if you try gradlew test --debug-jvm? (or gradle if not using the wrapper)

    – Slaw
    Nov 16 '18 at 7:04











  • @Slaw I tried it. Did not work. thanks anyways.

    – Muneer Y
    Nov 16 '18 at 17:24
















0















I have a spring boot project (Java 8, JUnit 4). I am using IntelliJ for IDE. My test passes when I run from within IntelliJ but fails when I run it from command line using gradle test command. So I am trying to remote debug my Junit test. I have breakpoints set. But when the test is executing the debugger is not stopping at the breakpoints. This is what I have done so far:




  1. I have created a remote debug configuration in IntelliJ with port as 5005

  2. I am running this command: gradle test -Dtest.debug on command line

  3. I see build output that the build is waiting for the debugger to connect to port 5005 and the process suspends

  4. At this point I run my remote debug configuration and it successfully connects to port 5005

  5. After this the JUnit test is executed but the debugger does not stop at the breakpoints.


In fact when the test is running the breakpoints on the junit test are changing to lite gray color. This tells me that the JVM IntelliJ debugger got connected to did not have the executable code for my test. Gradle is spinning off multiple JVMs I believe and IntelliJ is connecting to the wrong one. How can I validate this?



How to make debugger stop at the breakpoints? Really appreciate someone's help.










share|improve this question

























  • Not sure if it'll make a difference, but what if you try gradlew test --debug-jvm? (or gradle if not using the wrapper)

    – Slaw
    Nov 16 '18 at 7:04











  • @Slaw I tried it. Did not work. thanks anyways.

    – Muneer Y
    Nov 16 '18 at 17:24














0












0








0








I have a spring boot project (Java 8, JUnit 4). I am using IntelliJ for IDE. My test passes when I run from within IntelliJ but fails when I run it from command line using gradle test command. So I am trying to remote debug my Junit test. I have breakpoints set. But when the test is executing the debugger is not stopping at the breakpoints. This is what I have done so far:




  1. I have created a remote debug configuration in IntelliJ with port as 5005

  2. I am running this command: gradle test -Dtest.debug on command line

  3. I see build output that the build is waiting for the debugger to connect to port 5005 and the process suspends

  4. At this point I run my remote debug configuration and it successfully connects to port 5005

  5. After this the JUnit test is executed but the debugger does not stop at the breakpoints.


In fact when the test is running the breakpoints on the junit test are changing to lite gray color. This tells me that the JVM IntelliJ debugger got connected to did not have the executable code for my test. Gradle is spinning off multiple JVMs I believe and IntelliJ is connecting to the wrong one. How can I validate this?



How to make debugger stop at the breakpoints? Really appreciate someone's help.










share|improve this question
















I have a spring boot project (Java 8, JUnit 4). I am using IntelliJ for IDE. My test passes when I run from within IntelliJ but fails when I run it from command line using gradle test command. So I am trying to remote debug my Junit test. I have breakpoints set. But when the test is executing the debugger is not stopping at the breakpoints. This is what I have done so far:




  1. I have created a remote debug configuration in IntelliJ with port as 5005

  2. I am running this command: gradle test -Dtest.debug on command line

  3. I see build output that the build is waiting for the debugger to connect to port 5005 and the process suspends

  4. At this point I run my remote debug configuration and it successfully connects to port 5005

  5. After this the JUnit test is executed but the debugger does not stop at the breakpoints.


In fact when the test is running the breakpoints on the junit test are changing to lite gray color. This tells me that the JVM IntelliJ debugger got connected to did not have the executable code for my test. Gradle is spinning off multiple JVMs I believe and IntelliJ is connecting to the wrong one. How can I validate this?



How to make debugger stop at the breakpoints? Really appreciate someone's help.







java debugging intellij-idea junit






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 16 '18 at 17:35







Muneer Y

















asked Nov 16 '18 at 6:48









Muneer YMuneer Y

213




213













  • Not sure if it'll make a difference, but what if you try gradlew test --debug-jvm? (or gradle if not using the wrapper)

    – Slaw
    Nov 16 '18 at 7:04











  • @Slaw I tried it. Did not work. thanks anyways.

    – Muneer Y
    Nov 16 '18 at 17:24



















  • Not sure if it'll make a difference, but what if you try gradlew test --debug-jvm? (or gradle if not using the wrapper)

    – Slaw
    Nov 16 '18 at 7:04











  • @Slaw I tried it. Did not work. thanks anyways.

    – Muneer Y
    Nov 16 '18 at 17:24

















Not sure if it'll make a difference, but what if you try gradlew test --debug-jvm? (or gradle if not using the wrapper)

– Slaw
Nov 16 '18 at 7:04





Not sure if it'll make a difference, but what if you try gradlew test --debug-jvm? (or gradle if not using the wrapper)

– Slaw
Nov 16 '18 at 7:04













@Slaw I tried it. Did not work. thanks anyways.

– Muneer Y
Nov 16 '18 at 17:24





@Slaw I tried it. Did not work. thanks anyways.

– Muneer Y
Nov 16 '18 at 17:24












0






active

oldest

votes












Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53332767%2fnot-able-to-remote-debug-tests-in-intellij-when-executing-tests-using-gradle-tes%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53332767%2fnot-able-to-remote-debug-tests-in-intellij-when-executing-tests-using-gradle-tes%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Florida Star v. B. J. F.

Error while running script in elastic search , gateway timeout

Adding quotations to stringified JSON object values