From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,4a195a443fce793e
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news1.google.com!news1.google.com!proxad.net!infeed-1.proxad.net!news9-e.free.fr!not-for-mail
Date: Sun, 11 Dec 2005 20:06:38 +0100
From: Lionel Draghi <Lionel.nospam.Draghi@Ada-France.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR;
 rv:1.7.8) Gecko/20050513 Debian/1.7.8-1
X-Accept-Language: fr-fr, en-us
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: example of layered software?
References: <438cb166$0$21117$626a14ce@news.free.fr>
   <25a76$438db705$4995576$13285@ALLTEL.NET>
   <438e0f2d$0$21696$626a54ce@news.free.fr>
 <1134314348.920141.227440@g43g2000cwa.googlegroups.com>
In-Reply-To: <1134314348.920141.227440@g43g2000cwa.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Message-ID: <439c78c2$0$9709$626a14ce@news.free.fr>
Organization: Guest of ProXad - France
NNTP-Posting-Date: 11 Dec 2005 20:06:44 MET
NNTP-Posting-Host: 82.236.216.140
X-Trace: 1134328004 news9-e.free.fr 9709 82.236.216.140:52510
X-Complaints-To: abuse@proxad.net
Xref: g2news1.google.com comp.lang.ada:6836
Date: 2005-12-11T20:06:44+01:00
List-Id: <comp.lang.ada>

Marco a �crit :
> my suggestion:
> 
> To get started, synthetic test code is the way to go.

I wrote a small tool to create Ada packages, that I use in my "make check".
It eases package creation with precise dependencies.

For example:

    @create_pkg P1 spec -with P2 -with P3

will create:

    with P2;
    with P3;

    -- created by Create_Pkg v1.0
    package P1;
       null;
    end P1;

All my tests are based on those minimal packages, and my biggest test 
only involve half of them.
This is why I don't feel comfortable to release something without at 
least once real size testing.

> After that,
> "beta" release your tool so others can test it for you on real code and
> provide feedback. Since you are releasing the tool as free software
> then let others be your test team.

OK, but I want to reach a minimal useability level.
I'm not sure it's already the case, I have to think about it.

-- 
Lionel Draghi