What is the best way that run test codes on fleet?...

# fleet

[윤동환]

What is the best way that run test codes on fleet?

Fleet does not support junit, kotest plugin until now…

[henrik]

I wonder about the same thing: Is it possible to create a run configuration for a file? e.g. right-click a kotest spec, select my custom test runner -> which would run gradle test --tests ${filename.replace(".kt", "")}

[henrik]

I figured that something like this works:

{
    "configurations": [
      {
        "type": "gradle",
        "name": "Run Gradle test",
        "tasks": [ "test" ],
        "args": [ "--tests", "$FILE_NAME_NO_EXT$"],
        "workingDir": "$PROJECT_DIR$",
      },
    ]
}

I found the env variables at https://www.jetbrains.com/help/fleet/built-in-macros.html.

[윤동환]

@henrik is that work?

i wrote run.json file under .fleet dir and added snippet what you wrote abobe

[윤동환]

message has been deleted

[henrik]

that should work I think

[henrik]

it will run gradle test on the last file you have/had open in fleet

[윤동환]

ummm…

[henrik]

oops, had a typo in args. need to split it up into an array (see edited above)

[윤동환]

i did! thank you for your help Henrik!!

[henrik]

you're welcome :)

[윤동환]

image history for someone who need help.

the run.json file should be located under .fleet dir

[윤동환]

message has been deleted

[henrik]

This doesn't work for multiprojects, though. There aren't any macros to specify the subproject dir, so I have to use a custom script for that:

{
            "type": "command",
            "name": "Gradle test",
            "program": "$PROJECT_DIR$/tools/bin/gr",
            "args": [ "test --tests $FILE_NAME_NO_EXT$"],
            "workingDir": "$FILE_DIR$",
        },

[henrik]

(the gr scripts figures out which project the test is in and runs gradle -p subProjectDir ... )

[henrik]

(but this way I don't get the nice test view in fleet, only console)

[윤동환]

ah my project is single module project.