howto run unittest of a single module in dub driven project?

[Basile B.]

On Sunday, 4 March 2018 at 12:22:35 UTC, Basile B. wrote:
> On Sunday, 4 March 2018 at 11:38:37 UTC, Basile B. wrote:
>> On Sunday, 4 March 2018 at 10:43:06 UTC, Arjan wrote:
>>> [...]
>>
>> In Coedit yes.
>>
>> 1/ The path to the other source (usually the <leading 
>> path>/src/ or <leading path>/source/) folder must be 
>> registered in the library manager.
>> 2/ Menu "Compilation" item "Run file unittests", which test 
>> the module that have the focus in the editor.
>>
>>
>> Relevant manual page:
>>
>> - http://bbasile.github.io/Coedit/features_runnables#other 
>> (The action Run file unittest is almost the same thing as a 
>> runnable, except that -unittest is added to the switches byt 
>> the IDE).
>> - http://bbasile.github.io/Coedit/widgets_library_manager : 
>> dependencies for single  module to be run or executed must be 
>> reistered here.
>>
>> And finally i can say that it works fine since i use this 
>> system for years.
>
> Actually i realize that i only work well when the project is a 
> library.
> And this is probably a limitation i could remove in the IDE.

NVM, will be in Coedit 3.6.4[1]. This will work for applications 
sources too, assuming the main in is app.d

[1] 
https://github.com/BBasile/Coedit/commit/f8c5e686c8c6aaa7dc2c770121767e3e59806a0e

Thanks for givin me the idea original poster.