Re: [Watinfixture-users] Not closing the browser leaves Fitnesse"running"

[Jeff P. <ka...@iw...>]

Oh wait - duh, you emailed the WatiNFixture list.  Sorry, Rob, I'm brain
fried.  It's been a rough week.

 

The Workflow commands have the command Sleep:

 


Sleep


Sleeps for the given number of milliseconds.

Command:

|sleep|<number of milliseconds to sleep| 

Example:

|sleep|5000| 

So you could add a sleep of 30000 to give yourself a 30 second pause to see
what is going on.

 

I started working on an updated web site that will hopefully ease finding
commands, and I need to kick myself back into gear on this project.

 

  _____  

From: Jeff Parker [mailto:ka...@iw...] 
Sent: Tuesday, September 11, 2007 11:07 PM
To: 'Rob MacFadyen'; 'wat...@li...'
Subject: RE: [Watinfixture-users] Not closing the browser leaves
Fitnesse"running"

 

Did you develop your own custom FitNesse wrapper for WatiN?

 

If you did, go get my project, WatiNFixture.  One of the fixtures I wrote
was a custom Pause with a timeout setting.  You can see how I did that and
adopt the code into your own.

 

  _____  

From: wat...@li...
[mailto:wat...@li...] On Behalf Of Rob
MacFadyen
Sent: Tuesday, September 11, 2007 8:36 PM
To: wat...@li...
Subject: [Watinfixture-users] Not closing the browser leaves
Fitnesse"running"

 

Hi,

 

If I setup a few simple UserAction test steps and do not finish the test
with "close browser" the browser display the Fitnesse results will remain
"waiting for http://localhost:8080/WatiN01?test...." (I'm running fitnesse
on port 80, my test script is called WatiN01). And further the FitServer.exe
process remains running indefinately.

 

The reason I'm not closing the browser is that I need to see what's going
on. I have a Verify Browse Navigated To that is failing... and I really need
to see the web page so I can tell what's happening. If I put the "close
browser" step in... well... the browser is gone so quickly all I can tell is
that I have some sort of an application error message being displayed.

 

Any suggestions? Any way to put a "pause" of some sort in there?

 

Regards,

 

Rob