Support Kotlin/JS vol. 2

[krzema12]

Hi Team!

I'm aware of #106 but I think it was closed prematurely. For me, the lack of gutter icons and in fact any IDE integration is a major pain point. I'm close to moving back to kotlin.test and leaving just kotest assertions library.

Implementation-wise, my intuition tells me that, contrary to what was suggested in the closed ticket, the individual tests can be detected by static analysis - no need to execute it. IntelliJ plugins API probably exposes some kind of AST or PSI that would be helpful in detecting e.g. invocations of test function inside FunSpec.

[sksamuel]

It's in the works. The PSI side is done. This is a JS project.

The outstanding issue is attaching the JDK to run the engine to the run configurations.

[stale[bot]]

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.

[krzema12]

@sksamuel could you share if there's any progress?

[stale[bot]]

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.

[krzema12]

@sksamuel is there still hope?

[sksamuel]

We are actively working on this. But it won't be Q2.

[stale[bot]]

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.

[krzema12]

It still would be nice to have it.

[sksamuel]

It's still on the roadmap.

On Fri, 12 Aug 2022 at 00:02, Piotr Krzemiński @.***> wrote:

It still would be nice to have it.

— Reply to this email directly, view it on GitHub https://github.com/kotest/kotest-intellij-plugin/issues/160#issuecomment-1212731764, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFVSGU4TZSNXIQD4QGTHM3VYXLHFANCNFSM5LVTP6MQ . You are receiving this because you were mentioned.Message ID: @.***>

[stale[bot]]

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.

[krzema12]

Bump.

[stale[bot]]

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.

[krzema12]

.

[stale[bot]]

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.

[krzema12]

Knock knock.

[stale[bot]]

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.

[krzema12]

Is it still on the roadmap? If yes, does it make sense to exclude it from auto-resolving?

[stale[bot]]

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.

[krzema12]

Robot, your resistance is futile, please stop auto-resolving this issue.

[lppedd]

This is the reason I'm still using kotlin.test.

What I'm missing there tho is https://youtrack.jetbrains.com/issue/KT-49141
@krzema12 feel free to upvote it.

[sschuberth]

Can we somehow help to get this done?

[sksamuel]

On the radar for 6.0 I already have nested test support for JS running through my own plugin, so that's the pre-requisite for running tests individually in the plugin.