Support postDebugTask property

[rubensa]

Provide support for postLaunchTask (like postDebugTask for launch configurations) property to launch a task at the end of testing.

This attribute should be set to the name of a task specified in tasks.json (in the workspace's .vscode folder).

NOTE: This would be the companion to preLaunchTask.

[jdneo]

Makes sense since we have postDebugTask for launch configuration. Would you like to share what kind of task you hope to run after testing?

Another problem I'm thinking is about the naming. Maybe we should call it postDebugTask as well to avoid introducing 'ambiguousness'

[rubensa]

No problem with the naming but I don't know why the naming preLaunchTask (launch) and then postDebugTask (debug) in the launch attributes.

In my case, In a multi-root workspaces configuration, for just one workspace folder, I'm running a docker-compose up (for ignite and postgres start) for tests that needs database access. I'd like to automatically call a docker-compose down task to tear down the databases just after the tests for that workspace folder has ended.

NOTE: It's also a pitty that I need to define the corresponding empty tasks in other workspaces for the extension complaining for non existing task on those workspaces (as the java.test.config referencing the preLaunchTask is defined at devcontainer.json level), but this is a different issue.

[jdneo]

I don't know why the naming preLaunchTask (launch) and then postDebugTask (debug) in the launch attributes.

I'm confused as well. 😂

Thanks for the information.

[jdneo]

@rubensa, I just released a pre-release 0.38.2023051002 containing this feature. Should be available in a few hours.

[rubensa]

Thanks @jdneo
I'll try it!

[rubensa]

@jdneo I tried it and works like a charm 👍

[jdneo]

Good to know, thank you for the update! 😁