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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,729e40fc9b658cc9,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-03 07:25:50 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: robeybd@npt.nuwc.navy.mil (Brian R.) Newsgroups: comp.lang.ada Subject: AdaCAST , APEX Ada and Clearcase Date: 3 Jun 2003 07:25:50 -0700 Organization: http://groups.google.com/ Message-ID: <2ee29912.0306030625.98208a3@posting.google.com> NNTP-Posting-Host: 164.223.71.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1054650350 12757 127.0.0.1 (3 Jun 2003 14:25:50 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 3 Jun 2003 14:25:50 GMT Xref: archiver1.google.com comp.lang.ada:38479 Date: 2003-06-03T14:25:50+00:00 List-Id: We are using VectorCAST's AdaCAST unit testing tool, their newest Release 3.0 in conjuntion With Rational Corp's APEX ada using Clearcase as the version control. The system is a SPARC Solaris Sunblade 1000 It seems that every time when performing, even the simplest of unit tests, the software attempts to rename the file, which is under clearcase view. It renames the file by adding vc_ to the original name. As the file is under clearcase, and for unit testing purposes, we do not want to original source code being changed. But if a file is checked out by a user, it will be renamed and cannot be undone unless, be reverted manually, to its original form before a unit test was created for the file. It also seems unless without allowing adaCAST to rename a file, which is in clearcase, whitebox testing cannot be performed unless the software in question is allowed to do so,... we do not want orignal source code being modified, Is there any way to resolve this issue and still allow us to unit test the code, safely, without alterations to the code itself, which adaCAST seems determined to do?