Idea unable to debug unit tests
Answered
I upgraded Idea last week to the latest version, IntelliJ IDEA 2019.3.2 (Ultimate Edition)
Build #IU-193.6015.39, built on January 20, 2020.
I have a Spring Boot Gradle project and when I try to run the unit tests via debug either via the Menu or ^D nothing happens. The Debug tool window does not come up, I see no errors, just nothing. Using the Run via the Menu or ^R works fine, it's just Debug that does not work. Debugging did work fine until I upgraded IDEA last week.
The behavior is the same whether I try to run them as Gradle tests or Unit tests.
Any ideas what may have changed?
Please sign in to leave a comment.
Does the workaround from https://youtrack.jetbrains.com/issue/IDEA-228180 help?
Are there any errors in the logs: https://intellij-support.jetbrains.com/hc/articles/207241085 ?
I'd report a bug at https://youtrack.jetbrains.com/newIssue?project=IDEA with the logs attached (Help | Compress Logs and Show in ...).
The workaround did not help because my CONFIG/disabled_plugins.txt file is empty so there was nothing to delete from it.
I do get a stack trace in the logs whenever I press the Debug button. It looks like this:
Looks like https://youtrack.jetbrains.com/issue/IDEA-231915. Please follow it for updates. See https://intellij-support.jetbrains.com/hc/articles/207241135 if you are not familiar with YouTrack.
Please also check if this workaround helps: https://youtrack.jetbrains.com/issue/IDEA-230493#focus=streamItem-27-3923076.0-0 .
Yes that workaround seems to work, I checked the "Show F1, F2, etc keys on the the TouchBar" box and restarted IDEA, and now I can debug the tests again. Thanks.
I have the same issue with unit tests in gradle project. Maven works fine.
Nothing is written to the logs if I try to start debugging by clicking on the bug (context menu in the left margin, or in Gradle tool window or in the header area).
Tried with "Run tests using" Gradle and also IntelliJ IDEA. After a whole day of restarting, invalidating cache, .... nothing changed. No logs, no hint, nothing.
Any help appriciated! (Went already through the links above, stackoverflow, ....)
idea information:
>I have the same issue with unit tests in gradle project.
The mentioned issue has ben fixed. It was also specific to macOS. You most likely have different problem. Could you please describe exactly your action, what happens after this and what is expected result? Screenshots/screencast would be helpful. Does it happen with specific project only?
Please also attach IDE logs (use Help | Collect Logs and Diagnostic Data action) after reproducing. Thank you.
Having same issue with gradle project and latest intellij version 2022.2.2 in Mac OS Monterey Version 12.5.1 in Apple M1 chip.
Though I can debug a normal class but cannot debug unit test.
Mohammad Khaer
Does this workaround help in your case?
If not, please provide additional details as per the comment above. You can upload everything privately to https://uploads.jetbrains.com and provide the upload id here.
Arina Efremova
Thank you so much for replying. I had a different cause actually. In Intellij unit test debug settings it was set to gradle. I changed this to Intellij. It works now.
But AWS Lambda code debug does not work. Do you have any workaround for this ? I have set up required things like docker, AWS SAM, AWS profile. Those are okay and unit test debug works. But lambda debug does not work but I can run the actual lambda.
Sure, no problem Mohammad Khaer
If you use this plugin, please note that it is developed and maintained by a third party, so any questions or problems with its functionality are best submitted to the plugin's own issue tracker.
Hi I am not using this tool for debugging. I just have AWS SAM, docker.
Not sure if this plugin is mandatory to debug AWS lambda.
Mohammad Khaer This thread is about IDEA being unable to debug unit tests. Let's keep it that way.
Please submit a new ticket to YouTrack providing all the details regarding your project (structure, frameworks, build tools), the kind of breakpoints you set and their location in code, entire run/debug output if applicable, logs (Help | Show Log in...) and screenshots.
Arina Efremova I understand. Just to share with everyone I solved my problem (cannot debug AWS Lambda function). It was due to Apache Camel Intellij plugin. Seems this plugin has conflict with AWS Lambda function debugging.
I uninstalled the plugin (Apache Camel Intellij plugin). Now I can debug my AWS lambda function in local.
I am likely facing the same issue. I am unable to debug JUnit tests.
My workaround is to use Gradle from the Terminal with the --debug-jvm argument and conducting remote debugging in IntelliJ.
I suspect it might be due to the complexity of the Gradle project I am working on. In much simpler projects, the debugger functions correctly.
IntelliJ IDEA 2023.3.2 (Community Edition)
Build #IC-233.13135.103, built on December 20, 2023
Runtime version: 17.0.9+7-b1087.9 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 4
Non-Bundled Plugins:
Lombook Plugin (233.13135.65)
Kotlin: 233.13135.103-IJ
Armstrong2free hello, do you experience the same issue as described in this ticket?
Sergei Riabinin Hello, no, I don't. The cause of my issue was probably related to the Gradle structure of the project which was not correctly loaded into IntelliJ (just my assumption). I tried using the IntelliJ's program execution instead of Gradle execution, and it worked correctly.
Now, the Gradle debugger from IntelliJ also works correctly. I believe that the ticket https://youtrack.jetbrains.com/issue/IDEA-246330/Autoscroll-Select-Opened-File-does-not-work-for-a-module-thats-in-another-module-which-is-inside-a-group could potentially contribute to solving the issue, but I am not entirely sure. (Another related ticket: https://intellij-support.jetbrains.com/hc/en-us/community/posts/7163308174866--Select-opened-file-button-does-not-work)
Armstrong2free fix for IDEA-246330 should be available on 2024.1 EAP 1, please try