TestFrameworkType.Starter — plan to include per-product modules after 262?

IntelliJ Platform
1

Hi,

In the IntelliJ Platform Gradle Plugin, TestFrameworkType.Starter still pulls only the six generic artifacts:

com.jetbrains.intellij.tools:ide-starter-squashed
com.jetbrains.intellij.tools:ide-starter-junit5
com.jetbrains.intellij.tools:ide-starter-driver
com.jetbrains.intellij.driver:driver-client
com.jetbrains.intellij.driver:driver-sdk
com.jetbrains.intellij.driver:driver-model

None of the new ide-starter-product-* artifacts (e.g. ide-starter-product-idea-ultimate, -pycharm, -goland, -rider, -android-studio, etc.) are pulled in by TestFrameworkType.Starter. As a result, after upgrading to 262 EAP (I see ide-starter-squashed-262.4852.50.jar ) , every UI-test setup that used IdeProductProvider.IU and now wants IdeInfo.IdeaUltimate fails to compile until you manually:

  1. Add the product-init artifact, e.g.:
    uiTestImplementation("com.jetbrains.intellij.tools:ide-starter-product-idea-ultimate:262.+")
  2. Add the FQN companion-extension import:
    import com.intellij.tools.ide.starter.product.idea.ultimate.IdeaUltimate

A few questions:

  1. Is it planned to extend TestFrameworkType.Starter to follow the 262 modular split — for example, sub-types like TestFrameworkType.Starter.IdeaUltimate, Starter.PyCharm, Starter.GoLand, Starter.Rider, etc., that pull the relevant ide-starter-product-* artifact in addition to the base six?

  2. If yes, what is the target plugin version? I want to know whether to keep the manual ide-starter-product-idea-ultimate dependency long-term or treat it as a temporary bridge.

  3. If no, what is the recommended pattern for plugin authors who run UI tests against a single IDE flavor? Is manually declaring the product-init artifact the intended public API, or is there a higher-level Gradle DSL planned (e.g. testFramework(TestFrameworkType.Starter, product = "IdeaUltimate"))?

Thanks!