---------------------------- EDIT: resolved. Another issue I'm having is running the unit tests thr...

# multiplatform

[ManApart]

----------------------------
EDIT: resolved.

Another issue I'm having is running the unit tests through the ide compilation instead of gradle compilation. Aka a run config using gradle and :cleanJvmTest :jvmTest passes the tests, but doing a junit 'all in package' (or running the jvm main file/entry point) test fails with an error that seems to indicate that the expect / actual classes aren't being correctly understood. I get a bunch of errors like the one below, despite the IDE finding the corresponding declarations / gradle-run tests passing.

\src\jvmMain\kotlin\core\history\SessionHistory.kt:9:15
Kotlin: Actual object 'SessionHistory' has no corresponding expected declaration

I'm wondering if I need to modify the run configuration somehow to understand the module structure?

I've done a hello world project with the same setup of having a jvm main call code in common that has expect/actual and it worked as I expected. So I assume I've done something wrong with this more complicated setup. I realize this is a more vague ask but would appreciate any pointers of things to track down. Thanks!

[ManApart]

IDE tests (not working) config:

[ManApart]

IDE run (not working) config:

[ManApart]

Works from the terminal as well as with the gradle tests run config:

[ManApart]

mind blown

@file:JvmName("QuestCommand") at the top of my main file fixed running the main in the ide. I wonder if I can do something similar for the unit tests.

[ManApart]

Followup: this fixed all my unit tests running through the ide config as well.