Re: [Oorexx-devel] Info on ooTest framwork and the 3.2.0 brach of the test suite

[Mark M. <mie...@gm...>]

On 1/12/08, Rick McGuire <obj...@gm...> wrote:
> On Jan 12, 2008 3:34 PM, Mark Miesfeld <mie...@gm...> wrote:
> > On 1/12/08, Rick McGuire <obj...@gm...> wrote:
> >
> > When you do this now, do you have the ooRexxUnit.cls directory in your
> > path?  It would seem like you'd have to.
>
> I've been lucky so far.  For the problems I've had to deal with, it was
> sufficient to run this outside of the debugger and just launch the debugger
> when it trapped.

This is on a tangent.  But, do you know how to run in the debugger
from the command line?  It was a tip I picked up a couple of years
ago.

Provided of course you have the MS Studio environment variables set
up, you can run an executable in the debugger from the command line.
Then you don't need to worry about setting up the correct environment
within Visual Studio.  The command line for VS 8 is:

devenv /debugexe <program name> <progam args>

When Visual studio opens up, select Start Debugging from the Debug menu.

Then of course you can use restart to start debugging from the program start up.

I usually don't have Visual Studio open, so I use the above method all the time.

So, provided you can execute the test suite from the command line, you
could run it in the debugger from the command line by doing:

E:\>devenv /debugexe rexx testOORexx <args to testOORexx>

That is actually how I run the existing test suite in the debugger.  I
do put the framework directories in my path.  But, if you are in the
same directory as rexx.exe you would be able to do, on my system:

E:\>devenv /debugexe rexx \ooRexxUnit\testOORexx <args to testOORexx>

>From my notes on how to do the similar thing in earlier versions:

>From the command line using VC6/7, type msdev <program name>.  You
might need to be in the same directory as the executable?

--
Mark Miesfeld