Could not find installation home path when running test using IJ 2025.2

Hi all,

I’ve trouble running Platform test using Intellij 2025.2, the error is the following:

Could not find installation home path. Please make sure product-info.json is present in the installation directory.
java.lang.RuntimeException: Could not find installation home path. Please make sure product-info.json is present in the installation directory.
	at com.intellij.openapi.application.PathManager.getHomePath(PathManager.java:113)
	at com.intellij.openapi.application.PathManager.getHomePath(PathManager.java:82)
	at com.intellij.testFramework.fixtures.IdeaTestExecutionPolicy.getHomePathWithPolicy(IdeaTestExecutionPolicy.java:105)
	at com.intellij.testFramework.fixtures.BasePlatformTestCase.getTestDataPath(BasePlatformTestCase.java:99)
	at com.intellij.testFramework.fixtures.BasePlatformTestCase.setUp(BasePlatformTestCase.java:43)
	at com.gitlab.msciachero.ActionsTest.before(ActionTest.kt:20)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at com.intellij.ide.starter.junit5.CurrentTestMethodArgumentsProvider.intercept(CurrentTestMethodArgumentsProvider.kt:53)

Same tests works well with 2024.3

In addition I’ve configured:

plugins {
    kotlin("jvm") version "2.2.0"
    kotlin("plugin.serialization") version "2.2.0"
    id("org.jetbrains.intellij.platform") version "2.7.2"

and this is my configuration of intellijPlatform:

intellijPlatform {
        intellijIdeaCommunity("2025.2") {
            useInstaller = false
        }
        jetbrainsRuntime()
        bundledPlugins(
            listOf(
                "Git4Idea",
                "com.intellij.platform.images",
                "org.intellij.plugins.markdown",
                "org.jetbrains.plugins.yaml"
            )
        )
        bundledModules(listOf("intellij.platform.vcs.dvcs.impl", "intellij.platform.tasks"))
        pluginVerifier()
        zipSigner()
        testFramework(TestFrameworkType.JUnit5)
        testFramework(TestFrameworkType.Platform)
        testFramework(TestFrameworkType.Plugin.Java)
        testFramework(TestFrameworkType.Starter)

    }

Did I miss something?

Mirko

Hi, @yuriy.artamonov or @jakub.chrzanowski any hint? I think there is some change in configuration between 2024.3 and 2025.2 but I wasn’t able to find any information.

Thanks a lot,

Mirko

You could help people help you by making a small reproducer project on GitHub

@yuriy.artamonov created a minimum project with the same error:

Just for info, I’m developing on Linux
``Linux mirko-thinkbook 6.16.4-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Aug 28 19:47:10 UTC 2025 x86_64 GNU/Linux
I’m just thinking to do a test on windows, maybe is something just related to linux.

Hello, any suggestion about this issue?

Hi all,

any hints for this problem?

Best regards,

Mirko

Hey @michael.262 , have you found the solution? I met this error as well when configured in CI pipelines.

No, I gave up on some tests (sic) but was the only options. Also moving the plugin in a split mode is even more difficult now to test.

Hey, folks! I took a look at this and the issue is caused by the PathManager which is used for resolving IDE location. Normally, it comes from the IntelliJ Platform you use for building the plugin, but – in the repro project — it is served from ide-starter-squashed artifact instead:

/Users/hsz/.gradle/caches/modules-2/files-2.1/com.jetbrains.intellij.tools/ide-starter-squashed/252.23892.409/2ceb94fe23faf9ff8a157ff87c3d0ea01873ab75/ide-starter-squashed-252.23892.409.jar

It is added to the classpath by the TestFrameworkType.Starter, and gets loaded yet before the IntelliJ Platform classes.
In order to fix that, Starter should be demoted in the classpath, but I’m not really sure yet how to handle it in a good manner.

As a workaround, you can:

tasks {
    test {
        useJUnitPlatform()
        systemProperty("java.awt.headless", true)

        jvmArgumentProviders += CommandLineArgumentProvider {
            listOf("-Didea.home.path=${intellijPlatform.platformPath}")
        }
    }
}

I’ll make that a part of the IntelliJ Platform Gradle Plugin, considering the test-specific IntelliJ Platform as well. Above code refers to the main IntelliJ Platform only.

Thanks @jakub.chrzanowski for the investigation and followup! Yes configuring idea.home.path works :grinning_face: