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.6 required=5.0 tests=BAYES_05,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,19633d014dacb027 X-Google-Attributes: gid103376,public From: Stephen Leake Subject: Re: Automatic Test Code Generator Date: 1996/11/27 Message-ID: <329C5A08.24AE@gsfc.nasa.gov>#1/1 X-Deja-AN: 201048038 references: <57ffin$il@mill.gdls.com> content-type: text/plain; charset=us-ascii organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA mime-version: 1.0 reply-to: Stephen.Leake@gsfc.nasa.gov newsgroups: comp.lang.ada x-mailer: Mozilla 3.0 (Win95; U) Date: 1996-11-27T00:00:00+00:00 List-Id: We looked into this recently. We found two commercial vendors (there are probably others): ** McCabe Associates 800-638-6316 http://www.mccabe.com ** Vector Software Inc. 401-295-5855 1130 Ten Rod Road Suite E-307 North Kingstown, Rhode Island 02852 fax: 401-295-5856 www.vectors.com McCabe makes a static path analysis tool, and a path coverage reporting tool (it instruments your code and gathers statistics). Vector makes a test suite generator. Both say generating the actual test case data is up to you; they wish they knew how to do it automatically - they'd get rich! The McCabe tool will help a lot in generating the test cases, and in verifying that you have actually covered each branch at the Ada source level. As another poster pointed out, it is not clear that this is the same as covering each instruction, particularly since adding the reporting code can affect what the compiler optimizer does. -- - Stephe