Re: [Watin-users] Watin-users Digest, Vol 42, Issue 12

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

I noticed the new version of WatiN is a LOT slower when using TypeTextthan
the previous version.

Is there a setting to speed that up?

Thanks in advance!

Greg Hile

  _____  

From: Jeroen van Menen [mailto:jv...@li...] 
Sent: Wednesday, December 16, 2009 2:42 PM
To: wat...@li...
Subject: Re: [Watin-users] Watin-users Digest, Vol 42, Issue 12

Yep,

change it to

if (IE.Exists<IE>(Find.ByTitle(Expected_Page_Id)).ToString() == "True")

or (best practice as of RC 1)

if (Browser.Exists<IE>(Find.ByTitle(Expected_Page_Id)).ToString() == "True")

HTH,

Jeroen

On Wed, Dec 16, 2009 at 8:33 PM, Duphorn, Darin (c)
<DDu...@cl...> wrote:

Jeroen,

I copied the information in the Lib directory to:

C:\Program Files\Watin\WatiN-2.0.10.928-net-2.0\source\lib

Now the

if (IE.Exists(Find.ByTitle(Expected_Page_Id)).ToString() == "True")
{
}

Doesn't seem to work anymore.

I guessing there was a change to this.

Thanks,

Darin

Message: 2
Date: Wed, 16 Dec 2009 15:56:27 +0100
From: Jeroen van Menen <jv...@li...>
Subject: Re: [Watin-users] Get the Current Browser Status Bar/ Status
       Text    Value
To: wat...@li...
Message-ID:
       <5aa...@ma...>
Content-Type: text/plain; charset="windows-1252"

Hi Darin,

With the latest code I mean the (development) code in the SVN repository in
Soureforge. If you just want the latest binaries, here is the trick:
Download the example code coming with my latest blog, you will find the
latests compiled version of WatiN in the lib directory of the zip file. This
is 99.99999999% the same is the upcoming RC1.

blogpost:
http://watinandmore.blogspot.com/2009/12/wrapping-complex-logic-in-control.h
tml
<http://watinandmore.blogspot.com/2009/12/wrapping-complex-logic-in-control.
html>example
code:
http://cid-7a759edaf62c1f79.skydrive.live.com/self.aspx/WatiNExamples/Creati
ng%20a%20DatePicker%20control.zip

<http://cid-7a759edaf62c1f79.skydrive.live.com/self.aspx/WatiNExamples/Creat
ing%20a%20DatePicker%20control.zip>
HTH,
Jeroen

On Wed, Dec 16, 2009 at 3:34 PM, Duphorn, Darin (c) <
DDu...@cl...> wrote:

>  Jeroen,
>
>
>
> Thanks for this.
>
>
>
> You mention getting the latest code.  Do you mean the WatiN-2.0.10.928 or
> is there a beta version?
>
>
>
> I currently using WatiN-2.0.10.928, and when I change the code from
> ._webBrowser to .WebBrowser I get the following error.
>
>
>
> WatiN.Core.Native.InterExplorer.IEBrowser does not contain a definition
for
> ?WebBrowser? and no extension method ?WebBrowser? accepting a first
argument
> of type ?WatiN.Core.Native.InternetExplorer.IEBrowser? could be found (are
> you missing a using directive or an assembly reference?)
>
>
>
>
>
> Thanks again for the start.
>
>
>
> Darin
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Darin,
>
> I think the code you have here is correct. With the latest code there is
> also a property on IEBrowser.WebBrowser which returns the IWebBrowser2
> instance.
>
> To wait until the StatusText has the right text, you could use
> the WatiN.Core.UtilityClasses.TryFuncUntilTimeOut class
>
> something like:
>
> var func = new TryFuncUntilTimeOut();
> var result = func.Try<bool>(() =>
>
>
>
((WatiN.Core.Native.InternetExplorer.IEBrowser)(browser.NativeBrowser)).WebB
rowser.StatusText
> == "something");
>
> You can set how long it should wait for succes in the constructor
>
> HTH,
> Jeroen
>
> On Tue, Dec 15, 2009 at 9:01 PM, Duphorn, Darin (c) <
> DDuphorn@cl...> wrote:
>
> > Below is what I get using VSTS 2008 Visualizer
> >
> >
> >
>
>
((WatiN.Core.Native.InternetExplorer.IEBrowser)(browser.NativeBrowser))._web
Browser2.StatusText
> >
> > I'm trying to write Code use C# that will give me the Status Text.
> >
> > I'm trying to synchronize my automated test, and the postback isn't
> > working correctly for this application, so I thought I could get the
> status
> > bar text and wrap a wait around that.
> >
> >
> >
> > Unfortunately, it easier said than done.
> >
> > Does anyone know how I can achieve this?
> >
> >
> >
> > Thanks,
>
>
> ------------------------------
> DISCLAIMER:
> Aan dit bericht kunnen geen rechten worden ontleend. Dit bericht is
> uitsluitend bestemd voor de geadresseerde. Als u dit bericht per abuis
hebt
> ontvangen, wordt u verzocht het te vernietigen en de afzender te
informeren.
> Wij adviseren u om bij twijfel over de juistheid of de volledigheid van de
> e-mail contact met de afzender op te nemen.
>
> Nothing in this email shall bind LinkiT in any contract or obligation.
This
> e-mail is for the intended addressee only. If you have received it in
error
> then please delete it and notify the sender by return e-mail. In case of
> doubt about correctness or completeness of this e-mail please contact the
> sender.
>
>
>
----------------------------------------------------------------------------
--
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Watin-users mailing list
> Wat...@li...
> https://lists.sourceforge.net/lists/listinfo/watin-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 3
Date: Wed, 16 Dec 2009 18:01:26 +0000
From: Julian Simpson <sim...@gm...>
Subject: Re: [Watin-users] Trouble with DialogWatcher and
       DialogHandlers: dialogs aren't being suppressed the way I expect
To: wat...@li...
Message-ID:
       <af9...@ma...>
Content-Type: text/plain; charset=ISO-8859-1

Sadly, this didn't work on IE8, at least.  I think HTA mode may ignore
the registry setting.  I think my next step is to review the
DialogWatcher code, make sure that the source I have matches the last
release from SVN, etc.

Best

Julian

2009/12/15 Jeroen van Menen <jv...@li...>:
> Smart! Hope it works
> Jeroen
>
> On Tue, Dec 15, 2009 at 2:43 AM, Syed Faizul Hasan - ERS, HCL Tech
> <Sye...@hc...> wrote:
>>
>> Hi Julian,
>>
>> You can disable these dialogs by modifying the IE options via the
>> registry. It is highly unlikely that this would also be limited by HTA
mode.
>>
>> Path:
>> HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main
>>
>> Key:
>> "Error Dlg Displayed On Every Error", set value to "no" ?to disable.
>>
>> Since the IE process is spawned on a remote machine, you could use
>> WMI(root\default:StdRegProv)to set this registry key.
>>
>>
>> HTH
>> Syed
>>
>>
>> -----Original Message-----
>> From: Julian Simpson [mailto:sim...@gm...]
>> Sent: Tuesday, December 15, 2009 1:26 AM
>> To: wat...@li...
>> Subject: Re: [Watin-users] Trouble with DialogWatcher and DialogHandlers:
>> dialogs aren't being suppressed the way I expect
>>
>> Hi Jeroen,
>>
>> I don't think I explained the situation comprehensively enough.
>> Sorry. ?Clarifications inline.
>>
>> 2009/12/14 Jeroen van Menen <jv...@li...>:
>> > Hi Julian,
>> > The most easiest way to get past this window is to not let it show by
>> > IE. In
>> > IE7 un check the following option:
>> > - Open ?Internet Options in Tools menu
>> > - Select the advanced tab
>> > - in the sub item Browsing, uncheck "Display a notification about every
>> > script error"
>>
>> The tool these guys use (and have a substantial test investment in) is
>> Selenium. ?The Selenium Remote Control conveniently spawns a browser
>> for you on a remote machine, but the way spawns IE is by running it in
>> HTA mode. ?My understanding of HTA mode is that you cannot set the
>> options like the one described above. ?I would be delighted to be
>> proved wrong. ?:)
>>
>> > Result is the same as when just closing every popup that shows up.
>>
>> Sure. ?I don't think anybody would mind which approach solved the issue.
>>
>> > Question is if you don't want to be informed about this issue by using
a
>> > dialoghandler to detect thee problems. I suspect that the current code
>> > isn't
>>
>> I guess we are looking for it to silently kill dialogs - my
>> understanding based on looking at the code is that the dialoghandler
>> will silently kill them (with the correct options set). ?That's what I
>> thought I had, but obviously not.
>>
>> > able to AttachTo while a dialog is shown. Please also report this issue
>> > on
>> > the bug tracker so I will not forget to try and fix this issue.
>>
>> My experiments support that suspicion. ?I've watched the WatiN
>> AttachTo() method fail to attach when a dialog is active. ?The method
>> will throw an exception after the configured timeout. ?Happy to raise
>> a bug about this if it helps.
>>
>> Best
>>
>> Julian.
>>
>>
>>
----------------------------------------------------------------------------
--
>> Return on Information:
>> Google Enterprise Search pays you back
>> Get the facts.
>> http://p.sf.net/sfu/google-dev2dev
>> _______________________________________________
>> Watin-users mailing list
>> Wat...@li...
>> https://lists.sourceforge.net/lists/listinfo/watin-users
>>
>>
>>
----------------------------------------------------------------------------
--
>> Return on Information:
>> Google Enterprise Search pays you back
>> Get the facts.
>> http://p.sf.net/sfu/google-dev2dev
>> _______________________________________________
>> Watin-users mailing list
>> Wat...@li...
>> https://lists.sourceforge.net/lists/listinfo/watin-users
>>
>> DISCLAIMER:
>> Aan dit bericht kunnen geen rechten worden ontleend. Dit bericht is
>> uitsluitend bestemd voor de geadresseerde. Als u dit bericht per abuis
hebt
>> ontvangen, wordt u verzocht het te vernietigen en de afzender te
informeren.
>> Wij adviseren u om bij twijfel over de juistheid of de volledigheid van
de
>> e-mail contact met de afzender op te nemen.
>>
>> Nothing in this email shall bind LinkiT in any contract or obligation.
>> This e-mail is for the intended addressee only. If you have received it
in
>> error then please delete it and notify the sender by return e-mail. In
case
>> of doubt about correctness or completeness of this e-mail please contact
the
>> sender.
>
>
>
----------------------------------------------------------------------------
--
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Watin-users mailing list
> Wat...@li...
> https://lists.sourceforge.net/lists/listinfo/watin-users
>
>

--
Julian Simpson
Software Build and Deployment
http://www.build-doctor.com
http://twitter.com/builddoctor

------------------------------

----------------------------------------------------------------------------
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev

------------------------------

_______________________________________________
Watin-users mailing list
Wat...@li...
https://lists.sourceforge.net/lists/listinfo/watin-users

End of Watin-users Digest, Vol 42, Issue 12
*******************************************

----------------------------------------------------------------------------
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Watin-users mailing list
Wat...@li...
https://lists.sourceforge.net/lists/listinfo/watin-users

DISCLAIMER:
Aan dit bericht kunnen geen rechten worden ontleend. Dit bericht is
uitsluitend bestemd voor de geadresseerde. Als u dit bericht per abuis hebt
ontvangen, wordt u verzocht het te vernietigen en de afzender te informeren.
Wij adviseren u om bij twijfel over de juistheid of de volledigheid van de
e-mail contact met de afzender op te nemen.

Nothing in this email shall bind LinkiT in any contract or obligation. This
e-mail is for the intended addressee only. If you have received it in error
then please delete it and notify the sender by return e-mail. In case of
doubt about correctness or completeness of this e-mail please contact the
sender.