[TIP] including (or not) tests within your package

[Olemis Lang]

On Wed, Aug 11, 2010 at 3:07 AM, holger krekel <holger at merlinux.eu> wrote:
> On Mon, Aug 09, 2010 at 23:54 -0700, Fernando Perez wrote:
>> [lost of valid points]
>> So yes, there's plenty of good reasons to make sure that a normal
>> user, post-install phase, can easily and cleanly run your tests and
>> copy/paste back a reasonably informative report.
>> [links and good points]
>
> Installing tests with an app is not the only and often not a sufficient way to
> achieve it (dependencies on needed-for-test libs and tools to begin with).
> Ideally, a user could grab a single-file script which is self-contained, runs
> the tests and produces an e-mail / web site submittable report, i guess.
>

At CI | issue tracking level at least it's possible , if the issue
tracker (and optionally the CI infrastructure) offer APIs then it's
possible to implement test runners that collect those results and
trigger workflows (e.g. possible using Trac + Hudson ;o) that trigger
(at a given time defined by workflow ;o) build job execution . The
only thing that may be needed is traceability to bind test cases to
requirements &| tickets &| ...

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article: