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,595c75298fbdce96 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,UTF8 Path: g2news1.google.com!news3.google.com!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Is Aunit helpful? Date: Fri, 13 Aug 2010 20:34:20 +0100 Organization: A noiseless patient Spider Message-ID: References: <8a1e58c0-2330-4475-8013-97df103dd85e@o19g2000yqb.googlegroups.com> <82r5ids1o9.fsf@stephe-leake.org> <20100805211820.52c18cb5.tero.koskinen@iki.fi> <8d166cfb-4850-42b6-ac25-d9ac00df7565@q35g2000yqn.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Date: Fri, 13 Aug 2010 19:34:21 +0000 (UTC) Injection-Info: mx01.eternal-september.org; posting-host="KCXegvZb5vh43D+f3BR6Ew"; logging-data="16263"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18JuBFr9AhY7biDeOTQp0LX9WherI+0iF0=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (darwin) Cancel-Lock: sha1:8I0mBtjz9PeXEFlsavnGNkwpk8A= sha1:qECGmTzCC2dQNhUQ1lx8quVXq+Y= Xref: g2news1.google.com comp.lang.ada:13235 Date: 2010-08-13T20:34:20+01:00 List-Id: "Yannick Duchêne (Hibou57)" writes: > About AUnit: just seen about what it is, how it is set up and how it > works. Seems a question is still pending : “how to be sure the test > cover all relevant case ?”. I do not see a way to be sure testing > cover all cases. That is the main limitation of this kind of > approach. May be this is nice for regression tests and tests cases > revealed during application's life time... however, I don't believe > this can be used too much soon in a development stage. Pretty sure > this is best used just after real use or deployment has been started. gcov (http://gcc.gnu.org/onlinedocs/gcc-4.5.0/gnat_ugn_unw/Code-Coverage-of-Ada-Programs-using-gcov.html#Code-Coverage-of-Ada-Programs-using-gcov) will help to tell which bits of code your tests haven't exercised at all. And it's free. For more capable test coverage tools you'll probably have to pay.