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

[Rob M. <rma...@rm...>]

Jeff,
 
I've been "mixing and matching". I started writing my own... thinking it
would be cool to offer a bridge framework that "talked" my application...
fixtures for creating "code tables" and fixtures for creating "code
values"... rather than doing this with WatiNFixture.
 
but... that's been relatively short lived... lots of weird problems... 
 
So... I figured it was time to "back up"... and now I'm using WatiN. So far
it's showing itself to be much more stable than my attempts (and pretty
cool... nicely done). 
 
Any recommendations in regards stability in doing my own custom fixtures? I
take it that there's some funky COM/interop weirdness that's causing things
to "hang" if the browser is not closed... any opinion? When gawking through
your code I saw you using a threadslot thingy to hold an instance of WatiN's
IE... as opposed to a simpler singleton... I was wondering why you went that
route?
 
I also seemed to have no end of difficult with working with dropdowns and
Select... exceptions about not finding values... when they clearly are
there. And some of these "sorts of exceptions" seemed to result in Fitnesse
"hanging"... very frustrating... especially since I don't seem to have quite
worked out how to get debugging "front to back" from VS2005 working.
 
Ah... I see the sleep command... that will do nicely.
 
Thanks a ton!
 
Regards,
 
Rob


  _____  

From: Jeff Parker [mailto:ka...@iw...] 
Sent: September 12, 2007 12:07 AM
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