when I upgrade my amper based project to 0.4 I hav...

# amper

[christophsturm]

when I upgrade my amper based project to 0.4 I have two problems: when i run it standalone (./amper test) it does not find tests (I use a junit platform engine), and when I run it via gradle (./gradlew check) it says Task 'check' not found in root project.

[christophsturm]

if anyone wants to take a look: https://github.com/christophsturm/isolation-chamber/pull/17/files

[Ivan Kubyshkin]

You need to include your modules in settings.gradle.kts

include("core")
include("integresql")
include("integresql-client")
include("postgresql-docker")

https://youtrack.jetbrains.com/issue/AMPER-393

[christophsturm]

thanks!

[christophsturm]

and the other problem? how do i get the standalone build to use my test engine? it worked with 0.3.x

[christophsturm]

its not a big deal, if the gradle build works and standalone does not work thats fine

[Joffrey]

Did you add project.yaml at the root of your project to list your modules?

[christophsturm]

Yes

[Joffrey]

Sorry, I could have just looked at the PR to get this answer.

[Joffrey]

I just cloned your repo and took a closer look, and I didn't realize you were using a special test engine here. I could indeed reproduce with Amper 0.4.0, and not with 0.3.1. I suspect the regression might be caused by some unfortunate changes in the classpath ordering (we currently add the kotlin-test-junit5 dependency when you specify junit: junit-5 in module.yaml). I couldn't get it to work even with junit: none, though.

[Joffrey]

To be frank, I don't think we considered the custom engine use case yet, and it might be worth opening a ticket for it for proper tracking.

[christophsturm]

classpath ordering should not matter, junit platform should try all the engines that are on the classpath.

[Joffrey]

Fair enough, probably not ordering per se, but a classpath change. I'll have a look. I opened this issue for tracking:
https://youtrack.jetbrains.com/issue/AMPER-945