Potential Partial Solution for "Errors with dub test"

[jmh530]

Addressing issue #15, I propose to add some configurations to the dub.json and then use preBuildCommands (I wasn't entirely sure if this is what should be used or preGenerateCommands) to run the python code necessary for the unittests.

When I make these adjustments, dub test works again on Windows and doesn't require additional work, but it seems to do the preBuildCommands multiple times (hence the comment above on preGenerateCommands).

I also believe there should be some way to detect that the commands fail, such as if python is not detected, and skip those tests. So that's why I'm referring to it as a partial solution.

[coveralls]

Coverage remained the same at 100.0% when pulling 79c66a9 on jmh530:jmh530-wintest into 5678bc4 on libmir:master.

[ShigekiKarita]

I also believe there should be some way to detect that the commands fail, such as if python is not detected, and skip those tests. So that's why I'm referring to it as a partial solution.

I have a plan to achieve this.

• in numir.io, if (exists("aa.npy")) { unit-tests } else { writeln("warning: not tested") }
• use cd test && python test.py ; cd .. instead of cd test && python test.py && cd .. to allow the ack of numpy

[ShigekiKarita]

@jmh530 would you check my solution updated from yours #21