Create test tree module by programmatically identifying test modules

[kirillzh]

An attempt to resolve #266.

I am actually not sure if this resolves the original issue. I tried the snapshot of the plugin locally and it did not help. This seems like a good change to have nonetheless?

I also tried to run unit tests locally to make sure they pass but ran into ./gradlew test:

PluginException: Trying to add extensions to non-registered file type Properties [Plugin: com.intellij.java]

[sksamuel]

An attempt to resolve #266.

I am actually not sure if this resolves the original issue. I tried the snapshot of the plugin locally and it did not help. This seems like a good change to have nonetheless?

I also tried to run unit tests locally to make sure they pass but ran into ./gradlew test:

PluginException: Trying to add extensions to non-registered file type Properties [Plugin: com.intellij.java]

I have found that isTestModule fails sometimes, even for source sets that are tests. For instance, am trying to do the same thing for the line markers.

Does this change work for you locally ?

[kirillzh]

Does this change work for you locally?

I don't think it does. I'm not very experienced with plugin development, but what I did is I built a snapshot plugin and installed it in IDE, didn't notice any effect.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Kantis]

@kirillzh you can use ./gradlew runIde to start an IDEA instance with your patch applied directly, for shorter turnaround times. The version started is determined by the line

val productName = System.getenv("PRODUCT_NAME") ?: "IC-241"