dub test overrides binary created by dub build

[ximion]

dub version: 0.9.24

When packaging software, it's quite common to run the build-time tests after the software was built.
Doing that with dub results in dub build and dub test to be executed in order.
Unfortunately, dub test seems to override the actual binary we install on the system later with the test-binary, which is pretty annoying.
Would it be possible to give the test-binary a different name, to make it not override the existing, previously built, actual binary?
Something like

dub build => foobar
dub test => foobar.test

Thanks for looking into this!

[s-ludwig]

By default, DUB picks the first library configuration and generates a test executable configuration from that. The executable is then named __test__<config>__. Only if the package recipe provides a custom "unittest" configuration, or only provides an executable configuration, the executable name will not be generated and may be the same as the usual executable name. However, IMO it is the task of the package author to decide on a proper executable name in that case.

[ximion]

When I reported this, the dub.json file I could use to reproduce this was:

{
    "name": "foobar",

    "sourcePaths": ["src"],

    "buildTypes": {
        "debug": {
            "buildOptions": ["debugMode", "debugInfo", "optimize", "inline"]
        },
        "debug-nooptimize": {
            "buildOptions": ["debugMode", "debugInfo"]
        }
    },

    "targetPath": "build",
    "targetType": "executable",
    "buildRequirements": ["disallowDeprecations"]
}

[s-ludwig]

Okay, it's the "targetType": "executable" in that case. But I guess it actually wouldn't hurt to let "dub test" override the "targetName" when generating from an executable configuration either...

[s-ludwig]

I've opened a PR: #1029

[MartinNowak]

Fixed by 9e73284