Re: [wtr-general] Re: text include assertion

2018-06-14 Thread Titus Fortner
A few recommendations from this thread. 1. Minimize the usage of `@browser.text` it results in more overhead than necessary and is more likely to provide brittle results (if at some point something else on the page says "English" for instance). Locate the exact element you want, or at least a

Re: [wtr-general] Re: An expected error generated on click does not occur on click(*modifier)

2018-06-14 Thread Titus Fortner
This would be a Chromedriver issue, so we'd need to see what commands are getting sent to the driver. Can you run both with `Selenium::WebDriver.logger.level = :info`? Is the html public that we could get them a reproducible issue? On Thu, Jun 14, 2018 at 6:29 AM Steve Parrado wrote: > > Has

[wtr-general] Re: text include assertion

2018-06-14 Thread Derick
I do something like this if I want to see an element or text is present or not `expect(@browser.div(id: language-selection, visible_text: 'English').present?).to be true` (or false) I also learned if you add the class id or name, it goes much more quickly instead of just visible_text.

[wtr-general] Re: An expected error generated on click does not occur on click(*modifier)

2018-06-14 Thread Steve Parrado
Has anyone seen similar behavior? I am still at a loss about this. On Thursday, June 7, 2018 at 12:00:07 AM UTC-4, Steve Parrado wrote: > > I was attempting to write a function that performed a ctrl+click so that > if the click caused a page navigation, it would be in a new window which >