I think we need to discuss the <automatic adding o...

# kotest-contributors

[Bernd Prünster]

I think we need to discuss the automatic adding of KSP. I tired hte cleaner appraoch @Emil Kantis pushed but for reasons I cannot fathom, JS tests are not running at all

[Bernd Prünster]

its clear that the listener needs to be configured as one of the first things, otherwise, it will not notice targets being added. I amended my local foo with a logger statement and it is logging properly. However, whenever I try to run JS tests, nothing happens, but compiling and "BUILD SUCCESSFUL"

[Bernd Prünster]

I just pushed to my demonstrator. no JS tests

[Bernd Prünster]

ok so apparently without any dedicated JS test sources, no JS tests are run whatsoever

[Bernd Prünster]

creating nested tests on JS trigger a Kotlin compiler bug

[Bernd Prünster]

not creating a nested test and thus not running into the compiler bug again gets me zero tests executed on JS

[Bernd Prünster]

even though there is now a ksp-generated kotlin file in the js folder where i's expect it to be

[Bernd Prünster]

ok nevermind, the JS file is there as expected even if no jsTest sources are there. but why is it not executed?

[Bernd Prünster]

feel free to poke around my demonstrator to debug, as I don't know what the issue is with JS not working

[Bernd Prünster]

I am now fairly confident that this is indeed a bootsrapping/startup bug in the kotest JS runner. I cannot fix that,

[Bernd Prünster]

i am unsure, but there seem to be kotest verification tasks missing for some targets