comp.lang.ada
 help / color / mirror / Atom feed
From: "Richard A. Maffei" <somewhere@work.com>
Subject: Re: debbuger or unit test tool
Date: Mon, 16 Feb 2004 08:06:43 -0500
Date: 2004-02-16T13:06:42+00:00	[thread overview]
Message-ID: <4030C062.E876FEBC@work.com> (raw)
In-Reply-To: f67d8aac.0402130831.130ef069@posting.google.com

orvio wrote:
> 
> Hi, I have a question for you.
> I'm using VectorCAST tool for unit test on WindowsXP. My problem is
> that VectoCAST doesn't create the ennvironment because of a constraint
> error during DATA_IF_ execution. I don't know why the error is
> generated because VectorCAST message is not detailed. Therefore I need
> of a debbuger for DATA_IF_ executable.
> Can anyone help me?
> In other case, can anyone suggest me another tool for ADA unit test?
> 
> P.S.
> The code is compiled with Objectada (AONIX) compiler, therefore
> ADAMulti is useless.
> 
> Excuse me for bad English.
> 
> Thanks to all.

We've experienced the same problems using AdaCAST with ObjectAda in a
Solaris environment:  numerous compile errors during the environment
build and very little/no information as to what caused it.  I resorted
to compiling the environment by hand when such things occurred.  All the
required source code is under the environment directory.  Compiling the
source files with any compiler switches you pass into the environment
should get you a better idea of the problem.  In the very least, you
will get an executable which you can run through the ObjectAda debugger.

I agree with the post about their support responsiveness. 
Unfortunately, due to us being on a classified system and our company's
policies about loading software onto such systems, it was often weeks
before we were able to load the patches.  In the end, we often had to
resort to ingenuity to overcome some of the problems.  So if you are
supported, I would suggest talking to VectorCAST first.

IMHO, AdaCAST is a very nice and extremely useful tool...for simple
systems.  Our biggest problem was attempting to use it in a system with
a big gnarly CORBA interface.  For units without any CORBA library
interaction, the environments generally built fine (with the annoying
exception of the tool inserting Text_IO calls in illegal places in task
rendezvous).  The tool's intuitive interface and simple scripting made
thorough testing easy (and a bit fun even! [ok, I'm pathetic]). 
Unfortunately, because of the CORBA problems (plus the fact that many
people were disappointed that the tool does not automagically do all
your testing for you), we have stopped using it.

I hope this helps you.

-- 
Richard A. Maffei
richard~a~maffei lmco~com
(replace '~' with '.' and ' ' with '@')



  parent reply	other threads:[~2004-02-16 13:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 16:31 debbuger or unit test tool orvio
2004-02-13 17:02 ` Reivilo Snuved
2004-02-16 10:40   ` orvio
2004-02-16 14:04     ` Ed Falis
2004-02-13 20:11 ` Jeff C,
2004-02-14 17:11 ` Simon Wright
2004-02-14 17:21   ` Jeff C,
2004-02-16 13:06 ` Richard A. Maffei [this message]
2004-02-17  8:41   ` orvio
2004-02-19  9:07     ` Ian Gilchrist
2004-02-23 17:05     ` Info Aonix
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox