• Russel Winder (18/18) Mar 26 2014 Is it the case that the Dub recommended project structure is in fact the
• Atila Neves (8/24) Mar 26 2014 Since I use unit-threaded for my unit tests, I place them all in
• Dicebot (4/20) Mar 27 2014 I think one is expected to treat integration (or any non-unit)
• Dejan Lekic (4/20) Mar 28 2014 I use precisely the same structure as my Maven projects. It does

Russel Winder <russel winder.org.uk> writes:

Is it the case that the Dub recommended project structure is in fact the
canonical D project structure?

The Dub recommended structure doesn't mention test code as opposed to
application/library source code, is it the case that the assumption is
that all tests are in the modules using built-in unittest and that there
are never any external tests?

What about integration and system testing?

cf. The canonical jvm language project structure is

	src/main/<language>
	src/test/<language>
	src/integtest/<language>

Thanks.

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

"Atila Neves" <atila.neves gmail.com> writes:

Since I use unit-threaded for my unit tests, I place them all in
a directory called "tests" at the root directory of the project.
I haven't written integration tests yet for any D project and was
wondering myself what I would do.

Mine might be a special case, I don't know who else uses a unit
testing library.

Atila

On Wednesday, 26 March 2014 at 16:13:15 UTC, Russel Winder wrote:
 Is it the case that the Dub recommended project structure is in 
 fact the
 canonical D project structure?

 The Dub recommended structure doesn't mention test code as 
 opposed to
 application/library source code, is it the case that the 
 assumption is
 that all tests are in the modules using built-in unittest and 
 that there
 are never any external tests?

 What about integration and system testing?

 cf. The canonical jvm language project structure is

 	src/main/<language>
 	src/test/<language>
 	src/integtest/<language>

 Thanks.

"Dicebot" <public dicebot.lv> writes:

On Wednesday, 26 March 2014 at 16:13:15 UTC, Russel Winder wrote:
 Is it the case that the Dub recommended project structure is in 
 fact the
 canonical D project structure?

 The Dub recommended structure doesn't mention test code as 
 opposed to
 application/library source code, is it the case that the 
 assumption is
 that all tests are in the modules using built-in unittest and 
 that there
 are never any external tests?

 What about integration and system testing?

 cf. The canonical jvm language project structure is

 	src/main/<language>
 	src/test/<language>
 	src/integtest/<language>

 Thanks.

I think one is expected to treat integration (or any non-unit) 
tests as simply one of sub-projects but I don't follow dub 
development much.

"Dejan Lekic" <dejan.lekic gmail.com> writes:

On Wednesday, 26 March 2014 at 16:13:15 UTC, Russel Winder wrote:
 Is it the case that the Dub recommended project structure is in 
 fact the
 canonical D project structure?

 The Dub recommended structure doesn't mention test code as 
 opposed to
 application/library source code, is it the case that the 
 assumption is
 that all tests are in the modules using built-in unittest and 
 that there
 are never any external tests?

 What about integration and system testing?

 cf. The canonical jvm language project structure is

 	src/main/<language>
 	src/test/<language>
 	src/integtest/<language>

 Thanks.

I use precisely the same structure as my Maven projects. It does 
make sense to me, as some of the projects I worked on mix 
languages (D with C, C++ and/or Java).