This one is a first for me. I run JS tests with `jsNodeTests` , they get executed after the project ...

# javascript

[Edoardo Luppi]

This one is a first for me.
I run JS tests with jsNodeTests , they get executed after the project is built, I run it a second time and I get
> Task protojsNodeTest UP-TO-DATE
With no tests executed.

Is this how it's supposed to work?
Both org.gradle.caching and kotlin.incremental.js are false

[jw]

This is regular Gradle incrementalism, yes. If no inputs have changed, the task is not run.

[jw]

Incremental JS is for the kotlinc-js task that compiles the JS

[jw]

Gradle caching is for caching outside the project directory and in the home directory so that doing build; clean build should run 0 tasks the second time

[Edoardo Luppi]

Okay, sounds fine!
Seems like this behavior is not retained when executing a single test, or while debugging the tests. I was just worried this would have broken my testing workflow inside the IDE, as I'm used to debug multiple times the same test just to follow line by line

[Edoardo Luppi]

Thanks for the other explanations btw