javier.vazquez

E2E - wrong alarms are being sent

Discussion created by javier.vazquez on Oct 15, 2010
Latest reply on Oct 21, 2010 by javier.vazquez

I have a few E2E scripts that basically look like the step below.  My problem is that instead of sending the alarm that I specify should the 'sync on image' time out, instead I get an alarm that says something like "step 1 failed to start on time" or " step 1 was delayed by 45 seconds".  If I am deliberately stopping this script from executing by perhaps putting in the wrong credentials into the application, shouldn't I be seeing my alarm below which would say "OWA triara Login failed to launch"?  Instead I'm getting the default timeout alarms.  If anyone could provide insight I'd appreciate it.

 

Regards,

 

javier

 

 

 

nimSetVariable("suppression_id","1triara_Launch")

target$="1triara_Launch"

nimQoSStart() 'Starts the QoS Timer

 

 

 

StartBrowser("IE", "https://owa.triara.com")

 

PAUSE  until

Bitmap("C:\Program Files\Nimsoft\e2e_scripting\scripts\vive_login.bmp")

InWindow("IEXPLORE.EXE|Internet Explorer_Server|Microsoft Outlook Web Access 01 - Windows Internet Explorer|1",2)

PauseFalse

nimQoSStop() 'Stops the QoS timer.

nimQoSSendNull(target$) 'Send a Null Value

nimAlarmSimple (4,"OWA triara Login failed to launch") ' Sends a major alert that the script did not run.  The number 5 is critical 4 is major, etc

nimEnd()

OWA_cleanup()

End

EndPause

 

 

nimQoSStop()

nimQoSSendTimer(target$)

Outcomes