All my JS/Wasm browser/node tests fail when run fr...
# javascript
c
All my JS/Wasm browser/node tests fail when run from IntelliJ, but are succcessful when I run them in the CLI… Is it a known problem? If not, where should I look for to debug this?
Even with
--info
, there's nothing useful:
Copy code
> Task :gradle:templates:template-lib:jsBrowserTest FAILED
[KOTLIN] Marking task ':gradle:templates:template-lib:jsBrowserTest' as not up-to-date because the task has failed previously
Caching disabled for task ':gradle:templates:template-lib:jsBrowserTest' because:
  Caching has been disabled for the task
Task ':gradle:templates:template-lib:jsBrowserTest' is not up-to-date because:
  Task.upToDateWhen is false.
Build dafa340f-38f1-4519-b4eb-69c363f7ab93 is started
Build dafa340f-38f1-4519-b4eb-69c363f7ab93 is closed
0 problems were found storing the configuration cache.
a
@Roman Golyshev ^^
e
Which Kotlin version are you using? And is this using
kotlin-test
or some other framework?
c
Kotlin 2.2.21, TestBalloon 0.7.1. I don't think it changes anything in that mechanism, though. My best guess is that it's not managing to start the browser somehow, but I don't know how to get more information about what could be happening.
e
Doesn't TestBalloon have its own IDE plugin? It might be spawning by how that plugin is submitting the command or listening for results.
c
It does, but I'm using a Gradle run configuration with task
check
, I'm not using the plugin's run configurations
e
Ahhh then it might be outside of pure Kotlin's scope. I'd open an issue under
KTIJ
, however I don't think every test framework is automatically supported, even if you're launching a Gradle command and expect it to be "framework-agnostic".
c
Can you clarify why that may be? What I have: •
./gradlew check
in the CLI works •
./gradlew check
ran by IntelliJ fails without logs To me, this seems to point to it being an integration issue between IntelliJ and KGP?