Test Runner tab not showing
I know this has been asked before, but I'm on a much newer version (2023.1.4 Community Edition) of Intellij which doesn't have some of the settings the other posts mentioned.
For context, I had the Test Runner tab on my old Intel-macbook running Intellij 2022.1.4 CE. I used OSX's Migration Assistant to migrate all files and settings to my new M1-macbook. I had to reinstall the latest Intellij 2023.1.4 CE and I even deleted my old .ijwb project folder and started fresh. Not sure if any old settings carried over that is preventing Test Runner from showing.
I have the JUnit bundled 231.9225.16 plugin which promises viewing results in the Test Runner tab of the Run tool window, but I don't see it when I run junit tests.
This is what I see when running tests
Please sign in to leave a comment.
Also, using Bazel sync so this plugin might also be relevant: Bazel for Intellij 2023.07.04.0.1-api-version-231
Hi,
Testing frameworks supported by IntelliJ IDEA are listed here: https://www.jetbrains.com/help/idea/testing-frameworks.html
Test Runner view is only supported for the run configurations corresponding to those frameworks.
Bazel plugin is developed by a third party, that's why if you use a run configuration provided by this plugin, it won't have all of the features that out-of-the-box frameworks have.
Hi Arina,
Is there a way for me to specify that I want to run my java unit tests under the JUnit framework plugin (which I have) instead of through Bazel so I can see the Test Runner tab?
For whatever reason, when I run the same test in Debug mode (shift + ^ + D on my Mac), the Test Runner shows up.
Notice it's still a Bazel test run.
Any reason for this?
Turns out Bazel test results are indeed integrated into the IDE's test UI.
As to the reason why it doesn't show the test tree correctly in run mode as opposed to debug, see if it helps to ask the Bazel team. It sounds like a plugin configuration issue.
For posterity, it was a bazel plugin issue.
https://github.com/bazelbuild/intellij/issues/5204
They've fixed in the latest version `2023.07.18.0.1-api-version-231`