Search results for query: *

Being able to automate regression testing with PROCOMM is not impossible. This is how I managed to do it. I want to be able to write to the DOS command line: pw5 test.was PWEXIT and have the PWEXIT argument be interpreted by my script to tell Procomm to shut down. I also want to be able to...

If I run the following from the dos command line: c:\Programs\Symantec\ProcommPlus\PROGRAMS\PW5.EXE EXEC_UTC_01.was It will start procomm and run the .was file I have been using pwexit to cause procomm to shut down when the script is finished, but I would prefere not to use pwexit. Anybody...

c:\Programs\Symantec\ProcommPlus\PROGRAMS\PW5.EXE EXEC_UTC_01.wax If I run the above line in a dos window, it will start up procomm and run the .was file. When the .was file finishes the procomm program is still running. Is there a command line argument I can add to the end of the above dos...

Has anybody got a .dll that would support using regular expressions when doing a "waitfor" or a "when target"?

Well maybe that isn't so bad considering the economy is so bad - or should I say that there are so few jobs and so many H-1B programmers working in the USA and so many companies outsourcing their work to India. Did you know that a genius type PhD software guru in India makes about $16,000 a...

What you provided works fine. thanks Maybe I was just getting to fried last night and I just thought it didn't work.

This was my final solution: In the file common.inc which is included by all of my .was files I put in the line ; #define BATCH -1 By leaving in or removing the ";", you can specify using the BATCH mode or not. In all the other .was files, I put the following at the bottom of each...

When I issue a command to my BCB ( a medical diagnostic machine ) I can get back a varied response: As an example I use the following: waitfor(&quot;GuiInit state=INITIAL rc=0 sentTo =GUIBOX replyTo=<none> sender=EXEC type=2 value=0&quot;) even though I am only interested that the...

first thing is thanks.... second thing is.... I wish I had my old code ( blew it away ) to figure out what I did wrong. third thing is..... I will try this out - I am sure your right. It wouldn't make any sense otherwise.

actually I was using: logTransmitWait(&quot;DISPLAY_WORKFLOW_LIST ^M&quot;, createWatchString(&quot;vacWorkflow.fillstatus&quot;, 1)) as you suggest. I just made a typo in the original post. You say, &quot;should work&quot;... have you ever used this construct when programming with ASPECT?

I have: strfmt s0 &quot;%-33s%d&quot;, &quot;vacWorkflow.fillStatus&quot;, 1 logTransmitWait(&quot;DISPLAY_WORKFLOW_LIST ^M&quot;, s0) I would like to have: logTransmitWait(&quot;DISPLAY_WORKFLOW_LIST ^M&quot;, createWatchString(&quot;vacWorkflow.fillstatus&quot;, 1) func createWatchString ...

stupid me.... pwexit will do the job if it is the last statement in all of the &quot;prog main&quot; programs I am running. It is amazing what you can do if you read documentation. Thanks everybody for your help. have a good day. :-)

Actually what I should have said is that when the first version of Procomm runs the first .was script, the first instance of Procomm just sits there doing nothing. this means the .bat file sits waiting for the first instance to finish running and never starts up the next line in the .bat file...

I can get more flexibility out of creating a .bat file and putting the following in it: c:\Programs\Symantec\ProcommPlus\PROGRAMS\PW5.EXE EXEC_UTC_01.wax c:\Programs\Symantec\ProcommPlus\PROGRAMS\PW5.EXE EXEC_UTC_02.wax c:\Programs\Symantec\ProcommPlus\PROGRAMS\PW5.EXE EXEC_UTC_03.wax My...

I have about 30 .was files I would like to run overnight. Any tips on how to do this? Normally I use TestExpert to put all my test scripts in a harness that I can have run overnight, but I don't have much experience with Procomm/Aspect Scripting. Any help would be appreciated.

My original code was pretty bad. The following is what I am trying to accomplish. I commented out the code that depends on using a &quot;func&quot; and replaced it with straight in line code. The question is how to accomplish the same thing with a &quot;func&quot; and not use inline code...

The following doesn't work because you can't pass an array name as an argument to a func. Is there a way to accomplish what I am trying by passing a reference to the array I want to search with the &quot;func searchArray&quot;? Thanks for the help. proc main string myArray[10]...

I just gave up and put the following at the top of my script file. #include &quot;.\COMMON\common.inc&quot; This way, I know that when anybody using my scripts has their script load path set correctly, all the common.inc procs will be in the correct place. You can do what has to be done with...

The &quot;Compile Options&quot; allows you to set the &quot;Aspect Include Path&quot;. It only allows about 80 characters in this field. I defined the environmental variable &quot;PROCOMM_INC&quot; to be &quot;C:\cygwin\home\elmerf\projects\testScripts\LDM_UTs\COMMON&quot; Now I want to put...

The &quot;Compile Options&quot; allows you to set the &quot;Aspect Include Path&quot;. It only allows about 80 characters in this field. I defined the environmental variable &quot;PROCOMM_INC&quot; to be &quot;C:\cygwin\home\elmerf\projects\testScripts\LDM_UTs\COMMON&quot; Now I want to put...