No problem
On 26-Oct-2017 9:05 PM, "Titus Fortner" wrote:
> I can't tell if you are trolling or just intentionally missing the point.
>
> The use of the element method is never *required. You may prefer it for
> your own reasons, but that's not the same.
>
> I think I've made my reasonable reque
I can't tell if you are trolling or just intentionally missing the point.
The use of the element method is never *required. You may prefer it for
your own reasons, but that's not the same.
I think I've made my reasonable request clear, even if you don't understand
it. I'm done explaining this.
Non-standard usage? But still it's taking an advantages of WATIR,
b.element() is not completely equivalent to driver.find_element(), it does
the element_call so many things are taken care of!
On Thursday, October 26, 2017 at 5:20:12 AM UTC+5:30, Titus Fortner wrote:
>
> There are some good reas
>
> Instead of #click, what happens if you do #href instead? Do you see the
> difference in the results?
This comparison is no way related to what I am telling!
I am saying something which selenium has the capability to automatically
perform which we don't have to take care from our level(f
> You realize you are effectively trying to 'mansplain' to one of the
> developers of Watir why not to use a majority of the Watir API? If you
> are just going to use b.element all the time, instead of making use of the
> Watir API and object model, then what is even the point of using Watir
There are some good reasons to use watir 6+ even when not taking full advantage
of the location API. I'm behind on blogging all these things.
I just don't want to encourage non standard usage in our official mailing list.
--
--
Before posting, please read http://watir.com/support. In short: se
On Wednesday, October 25, 2017 at 12:30:36 AM UTC-7,
rajagopalanmadas...@gmail.com wrote:
>
> Please reject my last mail, I was wrong about b.link(link_text:
> 'something').click
>
> Read this one, I have explained the advantage of link: over xpath:
> b.element(text: 'something').click
>
>
> It w
Instead of #click, what happens if you do #href instead? Do you see the
difference in the results?
Regardless of whether you understand the reasoning, I'm asking that you not
tell Watir users to use the element method. If there is something that
can't be solved without the element method, then
I don't understand what you mean by " you don't care about the resulting
lack of encapsulation"? Care to explain?
What's wrong with telling the users the way it works? I am confusing
anything, I am pretty clear about what I talk
I am telling If they use
b.link(text: 'something').click
it w
We actually had a long discussion at the Ruby test code hackathon in
Toronto last month about the proper behavior of the #text and #text_content
methods and how they relate to the text locator (which handles String and
RegExp values differently). I came into it arguing for changing the text
loc
Please reject my last mail, I was wrong about b.link(link_text:
'something').click
Read this one, I have explained the advantage of link: over xpath:
b.element(text: 'something').click
It would create the selenium equivalent of
driver.find_element(xpath: "//*[noramlize-space()='something']").
All the selenium locators are WATIR's locators as well, I don't have to use
element method if you don't like it, I could use link method as well with
b.link(link: 'something').click
it will still call selenium equivalent of
driver.find_element(link: 'something').click
no difference, but when
two thumbs up on the below admonishment/advice.
On Tuesday, October 24, 2017 at 7:52:36 AM UTC-7, Titus Fortner wrote:
>
> If you want to use Watir without its powerful element location API, and
> use only the element method and only Selenium locators, you are more than
> welcome to do that.
>
If you want to use Watir without its powerful element location API, and use
only the element method and only Selenium locators, you are more than
welcome to do that.
But stop telling other users that it's the right way to do it or that it's
better, because it isn't.
Watir provides an easy way f
yes, that's what I am saying xpath usage must be the last one. If we could
use available selenium-webdriver locators then we need to prefer that one.
On Monday, October 23, 2017 at 7:28:06 PM UTC+5:30, Titus Fortner wrote:
>
> The only reasons not to use xpath are that it is hard to read, and
>
The only reasons not to use xpath are that it is hard to read, and difficult to
write such that it is not brittle. Neither of these apply to how Watir
implements its location system.
--
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
watir-g
It's better to relay on element(link: "Services") instead of using
link(text: "Services") because when we use link(text: "Services") WATIR
goes on to form the xpath. xpath must be the last chance when we can't use
any selenium locators.
On Thursday, October 19, 2017 at 8:00:22 PM UTC+5:30, Jus
>
> If you try to use something like browser.link(text: "Services").click, it
> says:
>
> "element located, but timed out after 30, seconds."
>
The problem here is that there are actually 2 services links on the page.
One is in the mobile nav menu (when the browser width is small) and one is
On Thursday, October 19, 2017 at 9:30:22 AM UTC-5, Justin Ko wrote:
>
> :link and :link_text are Selenium-WebDriver locators. Their support is
> quite limited in Watir. They are only accepted when using the #element
> method:
>
> browser.element(link_text: "Services").exists?
> #=> true
>
> brow
:link and :link_text are Selenium-WebDriver locators. Their support is
quite limited in Watir. They are only accepted when using the #element
method:
browser.element(link_text: "Services").exists?
#=> true
browser.element(link: "Services").exists?
#=> true
Instead, I would suggest using :text:
20 matches
Mail list logo