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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,313a106b8dd38f30 X-Google-Attributes: gid103376,public X-Google-Thread: f43e6,313a106b8dd38f30 X-Google-Attributes: gidf43e6,public From: Ray Blaak Subject: Re: RATIONAL TESTMATE for ADA Testing - Any experiences to share ? Date: 1999/05/22 Message-ID: #1/1 X-Deja-AN: 481025483 Sender: blaak@ns32.infomatch.bc.ca References: <374667df@news.compd.com> X-Trace: news.bctel.net 927417277 207.34.170.96 (Sat, 22 May 1999 16:54:37 PDT) NNTP-Posting-Date: Sat, 22 May 1999 16:54:37 PDT Newsgroups: comp.lang.ada,comp.software-eng X-Complaints-To: news@bctel.net Date: 1999-05-22T00:00:00+00:00 List-Id: "David Akister" writes: > I would like to know if anyone can share experience of using the Rational > Testmate tool with Rational Apex on UNIX. Of particular interest is the > management of code units, time taken developing and modifying test-sets and > flexibility of the system. I have used it on a large air traffic control project, and found it quite useful for unit testing within a subsystem. One can test against expected outputs, or write general test drivers that set pass/fail explicitly. If one controls the test outputs under CMVC, then one has a nice historical record of how tests pass/fail. Time taken developing tests is rather dependent on the unit being tested, rather than testmate itself (basically, testmate doesn't really get in the way). Testing code should be considered as official software units that get carefully developed with future maintenance and enhancements in mind, reviewed as part of the unit, and need to be budgeted accordingly. (The biggest mistake I saw was to see testing code written as if it was throw-away code -- it never was, and all too often cut/paste/spaghetti code need to be enhanced to test new unit changes). The best feature of testmate that I liked was the code coverage analysis, which highlights those code regions not executed in a test. Basically, testmate is a good tool, but one also needs a good development process to enforce 1) that things are tested at all, 2) how they are tested (i.e. what information needs to be in the test output, and what is deemed sufficient coverage, etc.), and 3) what kinds of test information needs to be saved. > Oh, and before I forget how does the system compare with other test suites > for ADA testing such as ADATEST and LDRA (for coverage metrics) ? I have not used them. -- Cheers, The Rhythm is around me, The Rhythm has control. Ray Blaak The Rhythm is inside me, blaak@infomatch.com The Rhythm has my soul.