Hello,
I've been using Watir for 2 days, and all was working fine until i got a
strange error. It must be tied down to the html code i guess
This is my code:
mainFrame.link(:text,"Recibir Documentos").click
cmdButtonGo = mainFrame.button(:name,"cmdGo")
puts cmdButtonGo
cmdButtonGo.click <-
Thank you Bret for your accurate answer,
I will upgrade to watir 1.5, but in the meanwhile i will comment out the
add_checker( navigation_checker ) line.
What exactly does this function do? Actually my question is, how safe is it to
uncomment?
Thank you Bret
For the others, thank you for
Bret,
I've updated to latest version of 1.5.1 and the problem has gone away. Thank
you so much for your help, it is the good community feedback that allows
companies like mine be able to rely on open products!!!
I really appreciate your time.
Thank you.
Hello,
I have the following VB script in my page, line 106:
if (trim(document.all("txtInitialDate").value) = "" or
trim(document.all("txtFinalDate")) = "")
This script performs fine when clicked on manually, however when i click on it
through watir, i get a runtime error in the vbs engine:
--
Hi Bret,
Thanks so much for your reply and sorry for not posting that code initially.
mainFrame.link(:url,%r{Report\.asp}).click
mainFrame.button(:name,"cmdGo").click
mainFrame.text_field(:name,"txtInitialDate").set("2/10/2006")
mainFrame.link(:id,"ViewReport").click
#previous step should open
I've just discovered another place where the same error comes up, however this
error does not disable the script like the other. (maybe because in the
previous the navigation occurs with a window.open whereas here a button is
clicked and the form is posted.)
the vbscript code is:
if len(trim(d
Bret, thank you for your reply.
Well yes, the error is in that IE.attach, however the cause comes from the
previous line, because it did not execute a window.open vbscript command.
The window.open did not get to execute because of an error when getting the
value property out of a [document.all(
Hi Bret, I tried with the .focus command but still the error persists.
I am now debugging the vb script more carefully and maybe i'll be able to
narrow it down.
Thank you so much for your tip, anyway.
-
Posted via Jive Forums
ht
Hello,
I'm in dire need to solve this issue, I might have to dump Watir altogether if
it is not resolved soon :((
I've definetly narrowed it down to some sort of type mismatch within the
vbscript engine. When i break the VBscript debugger, i cannot evaluate simple
vbscript dim variables, becau
Thank you for your reply and the helpful links Paul,
Yes, i reckon i am one of the few, nevertheless, i must auto-test the
application as it is, since we cannot afford any changes to the application
other than the ones we're already making.
I sure appreciate your time and patience.
Thank you v
Hello,
With the help of my coworkers, I've made some progress in identifying the
problem.
[b]It is definitely a type conversion error.[/b]
I should clarify that this is an intranet web application that only supports
IE, that is the reason why VBScript is acceptable.
Anyway, i changed my vbscr
Thank you all s much for your replies, i'll post what i'm doing in the hope
that you can replicate the error,
Here's my HTML
and the vbscript