From: Simon Wright <simon@pushface.org>
Subject: Re: AUnit harness project and directory structure
Date: Fri, 18 Oct 2013 12:56:20 +0100
Date: 2013-10-18T12:56:20+01:00 [thread overview]
Message-ID: <ly38nyrdwb.fsf@pushface.org> (raw)
In-Reply-To: 4a87105b-cc34-4bcc-9981-90b2bc8711a8@googlegroups.com
Christoffer Holmstedt <christoffer.holmstedt@gmail.com> writes:
> As an example I'm looking at the very basic "calculator" example that
> comes with GNAT GPL. harness.gpr is put in the root folder and the
> actual code that is to be tested is put in the tested_lib/ folder,
> which is its own project.
>
> When I've used test frameworks in other languages (python/Java) I've
> been able to completely move all test specific files out from the src/
> folder. Is this possible with AUnit?
Certainly. See for example the structure at http://goo.gl/nUyYwY
> Any guidance concerning the AUnit structure and best practice is much
> appreciated.
Not sure about best practice, but this sort of structure seems entirely
natural to me.
next prev parent reply other threads:[~2013-10-18 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 9:04 AUnit harness project and directory structure Christoffer Holmstedt
2013-10-18 11:56 ` Simon Wright [this message]
2013-10-20 15:45 ` Stephen Leake
2013-10-20 16:58 ` Christoffer Holmstedt
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox