And other thing I want to point it out here is implicit wait.
Here you have talked about implicit and explicit wait
http://watir.com/docs/waiting/
You have mentioned about the implicit wait here, but this is not implicit
wait at all for WATIR, WATIR has nothing to do with implicit wait,
Thank you Titus!
On Monday, August 14, 2017 at 7:47:23 PM UTC+5:30, Titus Fortner wrote:
>
> That definitely needs to be updated. Watir 6+ makes the use of selenium's
> implicit wait functionality completely unnecessary / actively bad for the
> reasons you describe.
>
>
>
> On Aug 14, 2017
When I write
b.window.maximize
for chrome browser it's throwing the following error.
C:\Ruby23\bin\ruby.exe -e $stdout.sync=true;$stderr.sync=true;load($0=ARGV.
shift) C:/Users/rajagopalan.m/RubymineProjects/SeleniumLearning/Contact/
Example.rb
Hi it's working but it's not returning the string as you said, it's
returning the TableRow object
#
On Thursday, August 17, 2017 at 12:42:40 PM UTC+5:30, Titus Fortner wrote:
>
> Good catch. Only a tr can have a cell method.
> The correct call is therefore:
> browser.td(text: "John
Titus,
cell_name = browser.td(text: "John Smith")
cell_name.column_header
# => "Full Name"
It's not returning the string(Full Name) as you have explained, it's
returning table row object.
On Thursday, August 17, 2017 at 12:42:40 PM UTC+5:30, Titus Fortner wrote:
>
> Good catch. Only a tr
*See @js ? This is what I get for not copy/pasting the specs I write into
the documentation / blogs, like I told you to do. :-D*
I don't understand what you have written here
*Yeah, I think column header should return text and it currently does not.
This would fix that:
Here it is
Train No.
Train
NameFromDeparture
To
Arrival
Dist.(Km)
Travel Time
M
TWT
FSS
Class
17235NAGERCOIL EXP
HSRA
18:25
SRT
03:49
454
09:24
2A
3A
SL
O,
16236TUTICORIN EXP
HSRA
22:25
SRT
08:29
497
10:04
2A
3A
CC
SL
O,new
Yes. But I wanted to tell something about the last release
set!
It's completely useful and it's brilliantly managed now by sending first
character and last character through selenium. I have checked with 3 lack
character and it drastically produces the result. It quickly enters all the
To be close it 's choosing but not reflecting in the select list. But
selenium select does the Job properly. I believe after the choose,
selenium is triggering something which Javascript fails to trigger that.
On Monday, September 4, 2017 at 12:23:48 PM UTC+5:30,
rajagopal...@gmail.com
I have written the below code
browser.select_list(:id, "ProductGroup").select!("Fire Products")
It's not choosing any option as well as it's not throwing any error.
I know this has been done through Java script and don't know why it's not
working.
--
--
Before posting, please read
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
I agree with you, but frame was intentionally designed that way and that's
what frame is being used. Raising the defect and fixing is not in my hand
according to this project.
Actually I worked in WATIR for first five years in my company but that was
watir-classic not selenium based watir.
>
> You have more than one iframe with an id of 'SearchPanel' on the same
> page?
yes, Exactly, I have three frame with an id of 'SearchPanel'.
And yes, you can build this with Watir API without using XPath
here it is
@b.element(id:
Then How would I access your code? After accessing my code, should I use it
in WATIR library to check how is the performance? By the way where is your
new code?
On Wednesday, December 13, 2017 at 8:22:53 PM UTC+5:30, Justin Ko wrote:
>
> Sorry, no, these changes are not available in 6.10.1.
>
I am saying WATIR forms the xpath internally when you pass a locator which
is not of selenium, for an example, text: locator
If you write a code
b.span(text: 'something').click
then WATIR would write the corresponding equivalent as below
driver.find_element(xpath:
This change available in recent water 6.10.1?
On Tuesday, December 12, 2017 at 11:39:51 PM UTC+5:30, Justin Ko wrote:
>
> Rajagopalan, would you be able to see if the changes I have made in
> https://github.com/jkotests/watir/tree/simplify_locator fixes the
> performance problem for
browser.element(:id, "navlist")
Is it a pop up?
And are you aware that `set!` function is using JavaScript not Selenium
send_keys?
On Friday, November 3, 2017 at 6:13:22 PM UTC+5:30, Jeff Nyman wrote:
> I have a Watir script that works against one of my sample sites. I'll
> provide that
This error is due to timeout for pageload, timeout to load the page was set
to 60 seconds, Is your browser taking more than 60 seconds to load the
google?
On Friday, December 8, 2017 at 10:44:42 PM UTC+5:30, 江南 wrote:
>
> Hi,
>
> I have tried the code below but my script just keep loading then
>
> It is known that using :visible_text will not have the same performance.
It has to iterate over elements, where as the Selenium ones would not. The
benefit of :visible_text is that we can apply it across all element types,
not just links.
Yes, it is increasing the performance ! But still
It's a railway ticket booking. There are many book now links are there and
all of them are visible, but it has to choose the first one but it takes
too long time to click that link but while I use lick locator it does click
instantly.
On Monday, December 11, 2017 at 7:59:05 PM UTC+5:30, Titus
Can you please pay a little attention to the ongoing conversation? The
conversation is not about using element() or using link() function, the
conversation is about performance issue while I use visible text. I am
ready to use visible text If it does the good performance but it's not
doing it,
When I use
b.element(link: 'Book Now').click
it says
2017-12-10 12:49:01 WARN Watir [DEPRECATION] :link locator is deprecated.
Use :visible_text instead.
Does that mean it would be removed in future?
because what I found is, visible_text locator is not working properly, it
clicks the link
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
> 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
>
> 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
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
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
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:
Thank you Željko
On Tuesday, October 31, 2017 at 1:55:50 PM UTC+5:30, Željko Filipin wrote:
>
> https://help.github.com/articles/creating-a-pull-request/
>
> Željko
>
> On Tue, Oct 31, 2017 at 8:16 AM, rajagopalan madasami <
> rajagopal...@gmail.com > wrote:
>
>> Hi,
>>
>>
>>
>> I am able to
Hi,
I am able to create 'new issue' but I couldn't create the pull request, It
shows the below screen, what should I do to create the pull?
I have attached the screen shot of my page please have a look at that.
--
--
Before posting, please read http://watir.com/support. In short: search
click performs selenium click but click! performs javascript click
I suspect the element you want click is not a click, that's what
@browser.a(id: "Employee_ID").click!
is not working
but
@browser.link(:xpath, '//*[@id="Employee_ID"]').click!
working.
when you write xpath, you don't
Ah sorry, I made a small mistake in last mail
Use this
p b.divs(class: "row applied-voucers-list".split).map {|div| div.div.span.
> text}
On Tuesday, July 3, 2018 at 5:36:15 PM UTC+5:30, NaviHan wrote:
>
> Hi All
>
> In fact I nailed it in parts by using
>
> div(:nav_div, class: "row
I will write in watir and then you may convert that code into your
pageobject code
p b.divs(class: "row applied-voucers-list").map {|div| div.div.span.text}
This will print two span text, look at carefully I used b.divs not b.div
On Tuesday, July 3, 2018 at 5:36:15 PM UTC+5:30, NaviHan
What are you saying me? I gave you the answer, did you try?
On Tuesday, July 3, 2018 at 5:51:20 PM UTC+5:30, NaviHan wrote:
>
> Thanks.
> The query is posted in the group now.
> https://groups.google.com/forum/#!topic/watir-general/mJ1IhrQWCxg
>
> Hi Raja
>
> In fact I nailed it in parts by
I am not stopping you, I asked you to convert that into your model.
On Tuesday, July 3, 2018 at 5:57:35 PM UTC+5:30, NaviHan wrote:
>
> I would like to use the PageObject gem..
>
> On Tue, Jul 3, 2018 at 10:24 PM, >
> wrote:
>
>> What are you saying me? I gave you the answer, did you try?
>>
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,
How can I write the corresponding WATIR CODE for this given below selenium
Code?
driver.switch_to.window driver.window_handles[1]
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before you
Hi Titus,
Thanks for reply. I don't believe that's not the only difference. For an
example, If you do selenium click on an option of a select_list, then it
would be chosen but Javascript script click towards the option doesn't
choose the option. We need to write corresponding Javascript code
HI Thanks for sharing this article. Please share here whenever you write a
new article, Thanks.
On Tuesday, August 7, 2018 at 12:07:41 AM UTC+5:30, Titus Fortner wrote:
>
> I just posted an article on the History of the Watir project.
>
> http://watir.com/history/
>
> Titus
>
--
--
Before
Hi Titus,
We have recently had the talk in Stackoverflow, where you have suggested me
this code
I tried using your code but when I reach b.close, it's closing the browser
totally not the tab which has opened recently so I couldn't connect to the
original window.
Please execute this code
A! Okay, Got it! Thank you Very much!
On Tuesday, August 7, 2018 at 8:56:29 PM UTC+5:30, Titus Fortner wrote:
>
> Oh no, I gave the right code: https://stackoverflow.com/a/51666596/4072371
>
> Also, original_window is stored for you, you don't need to create it.
>
> b.select_list(id:
Hi Justin,
We are also using this wait_for_ajax in one of our Project. You said
I would suggest adding the jQuery.active check to your browser's
> after_hooks. Ideally this would catch all (or at least most) of the
> problems.
>
May I know how to do this?
On Tuesday, August 7, 2018 at
Hi Titus,
don't you think when you use the block to switch to the new window, it has
to close while it comes out?
>
> require 'watir'
> driver = Selenium::WebDriver.for :chrome
> b = Watir::Browser.new driver
>
> b.goto 'https://services.wiltshire.gov.uk/PlanningGIS/LLPG/WeeklyList'
>
>
Ah! that's pretty interesting, I was not knowing this. So you say Once I
have written this code, this code will be executed after every click I do?
On Tuesday, August 7, 2018 at 9:54:17 PM UTC+5:30, Titus Fortner wrote:
>
> jquery_wait = lambda { |br| br.wait_until { |b|
That will be interesting, I am using as shown below,
>
> def selectAndWait(locator, value)
> select locator, value
> waitForPageLoad
> end
>
> def waitForPageLoad
> @b.wait_until(timeout: @Page_Load) {@b.execute_script("return
> (jQuery.active === 0)").eql? true}
> end
>
>
Let me try
Oh okay. But you said
The Executor class when implemented will open up a lot more flexibility.
So will it be lesser wire call after Executor class implemented? Can I add
after that?
On Tuesday, August 7, 2018 at 10:18:51 PM UTC+5:30, Titus Fortner wrote:
>
> No, your way is better if it is
Okay, I will be waiting for that then! There was a new project in my
company for which I convinced them to use WATIR instead of Selenium where I
had to implement this waiting behavior! Okay excited to see this new
feature to be added! Thanks.
On Tuesday, August 7, 2018 at 10:24:55 PM
Hi Titus,
Can you please look at this problem, This guy is using selenium Ruby
Binding directly, I suggested him using WATIR instead. He is facing some
issue while initialing with WATIR!
https://stackoverflow.com/questions/51725080/issue-with-attempting-to-run-a-test-using-chromedriver
On
Full Stack Trace
C:/Ruby/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.13.1/lib/selenium/webdriver/remote/response.rb:69:in
`assert_ok': Invalid internal element ID requested:
1981667e-660a-4b45-becf-98e2ebf7c71d
(Selenium::WebDriver::Error::NoSuchElementError)
from
hi,
I started running in IE today. I have a select list, when I select an
option, onchange event of that select_list would refresh the page,
selection is happening properly, but at the end the selection, this error
was thrown,
Selenium::WebDriver::Error::NoSuchElementError: Invalid internal
Hi Titus,
I am getting this warning while I execute this code
>
> @b.span(class: "spinner").wait_while(&:present?)
>
>
2018-09-05 12:26:45 WARN Watir [DEPRECATION] ["stale_present"] Checking
`#present? == false` to determine a stale element is deprecated. Use
`#stale? == true` instead.
If I
>
> element.wait_while(&:exists?)
No, this wouldn't work, I have to wait until the element is visible,
element becomes invisible when loading completes.
And also, I am checking whether element is visible or not, I am checking
whether previously located element exist in the DOM. So this line
Okay, I disabled that notification!
On Wednesday, 24 October 2018 13:21:47 UTC+5:30, Titus Fortner wrote:
>
> Periodically RubyMine will use the wrong method to do its analysis. There
> must be another button method somewhere in your required files that doesn't
> take any parameters. No idea
You can see the pic below, it's happening only when I open chrome browser,
it's not happening for firefox.
[image: Untitled.png]
On Wednesday, 24 October 2018 13:01:26 UTC+5:30, Titus Fortner wrote:
>
> If you click on the line you should see a small red light bulb pop up on
> the left
Hi Titus,
When I type
b.button(class: "login-button").click
Rubymine shows this
[image: Capture.PNG]
There is a red colour underline RubyMine does only when I use b.button(),
it's not coming when I use b.element(). May I know the reason?
--
--
Before posting, please read
[image: Untitled.png]
On Wednesday, 24 October 2018 13:01:26 UTC+5:30, Titus Fortner wrote:
>
> If you click on the line you should see a small red light bulb pop up on
> the left that you can click to find out what RubyMine doesn't like.
--
--
Before posting, please read
Hi Titus,
Here is the gist url
https://gist.github.com/Rajagopalan-M/ba78aed6342c61d07968cfe195d3f4de
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before you ask, be nice.
Hi Titus,
I face the same problem again in another place. I created a gist for this.
Can you please confirm this whether it's a same issue and your fix would
resolve this problem ?
https://gist.github.com/Rajagopalan-M/47a9381bf82ca2468539a5bc1189ba40
--
--
Before posting, please read
Hi Titus,
I am facing weird problem,
When I try to click the element, even after page arrives properly, it is
waiting for 60 seconds and not clicking the button sometimes, it throws
below error. but 4 out of 10 times it happens and rest of the time it runs
successfully. What might be the
Hi Titus,
This line
@b.div(id: "spinnerOverlay").wait_while(&:present?)
line gets timeout in 30 seconds, can you tell how to set my timeout here?
and I have written this
'' while getElement(locator).obscured?
getElement(locator).click
Is there any other better way to write this code?
Hi Titus,
something goes terribly wrong while watir waits for element to exist. Even
after page loads completely, button clicks waits for 30 seconds and reports
me element doesn't exist. So I did this.
begin
b.button(id: 'something').click
rescue
b.button(id: 'something').click
end
I put a
Hi,
I am sorry, It works fine. And you are absolutely right. Yes.
b.element(visible_text: 'Sessions').click
>
Takes much time
but
b.link(visible_text: 'Sessions').click
>
Takes very less time.
On Sunday, September 2, 2018 at 11:45:04 PM UTC+5:30,
rajagopal...@gmail.com wrote:
>
>
Sure, I will be in office tomorrow, so I will taking that element html and
posting it here.
I have posted a question in Stackover flow, can you please answer me there?
https://stackoverflow.com/questions/52130793/select-method-and-option-method-works-differently
On Friday, August 31, 2018 at
Hi Titus,
You asked me to use visible_text in the place of link locator, actually it
works fine but when you go deeper to search more and more link using this
visible_text: it takes so much time even though it's wrapped up with
customized method like link(), so please don't remove link:
I have succeeded to set the download folder for chrome and it's perfectly
doing it's Job, but I couldn't do it for firefox
I have written the following code for chrome
client = Selenium::WebDriver::Remote::Http::Default.new
client.read_timeout = @Page_Load # seconds
prefs = {
download: {
Titus and Justin,
The line of code I executed
@b.select_list(id: "salutation").select value["User Title"] //value["User
Title"]="Mr"
Error I get
2018-12-20 15:24:44 WARN Watir [DEPRECATION] ["stale_exists"] Checking
`#exists? == false` to determine a stale element is deprecated. Use
Hi Justin Ko,
What other detail you specifically want from me ? Actually the same code I
am running in WATIR 6.14 and it's running fine but it's throwing error when
I use WATIR 6.16.
On Friday, 21 December 2018 21:07:33 UTC+5:30, Justin Ko wrote:
>
> Hi Raj,
>
> I think we still need more
Hi, Yes, as you are saying, it's only happening in Chrome. I had been using
the version of 2.43 and now I have upgraded to the recent version 2.45 but
still I face the same problem. And no, I am not using headless mode.
On Friday, 28 December 2018 18:59:43 UTC+5:30, Titus Fortner wrote:
>
> Is
Hi Titus,
When I run my project, this message always shows up before I run my program
but no hindrance to my running. Do you have any idea as to why this shows
up?
DevTools listening on
ws://127.0.0.1:59735/devtools/browser/8c6c9817-6a06-465a-8ff0-9950fcbc8149
Just wanted to tell you, one more gem was released for page object, did you
check that out? Its watirpump.
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before you ask, be nice.
You are perfectly correct, yes wait_while(&:exists?) will do the same Job, I
have not noticed when you explained me first time.thanks.
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before you
Yes I saw that in your article, that's best idea. Thanks.
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before you ask, be nice.
watir-general@googlegroups.com
I would like to say , this is such a perfect clarity! Yes this is the way
wait has to work.
On Thursday, September 13, 2018 at 8:57:57 PM UTC+5:30, Titus Fortner wrote:
>
> Ok, yes. This is a slight simplification, but think of Watir waiting for
> what makes the most sense for the provided
hi Titus,
b.select_list().select is not working in 6.16 but it's working 6.14.
So I have written
`b.select_list().option.select` and it's working fine. So it's a clear bug
in WATIR 6.16
--
--
Before posting, please read
hi, Is there any WATIR module is defined to use ActionBuilder. For an
example, How can I do the following code in WATIR?
driver.action.click(element).perform
Any WATIR way of performing the above operation?
--
--
Before posting, please read
No I don't know what library is being used to create this selectlist.
Options are coming into existence when I click that select_list(so it
doesn't exist in the HTML page until I click select_list).
On Thursday, 4 April 2019 20:28:24 UTC+5:30, Justin Ko wrote:
>
> Do you know what library is
Hi Titus,
You said None of the interpreter language can't be compiled and traformed
into Exe file a few days ago in another conversation but today I find
people those who uses Python can compile and producing the exe file. What
do you say for this? Do we have some way to achieve the same?
--
Please tell me which browser are you using? Downloads works perfectly for
Both Chrome and Firefox. I will tell you how, but you first let me know
which browser are you using
On Tuesday, 10 October 2017 23:07:19 UTC+5:30, James Eldridge wrote:
>
> Following this method from watirs guides
>
>
Hi Titus, there is no problem in downloading the files. It works perfectly.
If you still find a problem downloading the files, Please let me know I
will tell you something which you might have missed it.
On Thursday, 31 January 2019 23:57:04 UTC+5:30, Titus Fortner wrote:
>
> Yeah, I don't
Hi, Thank you , I will check it out.
On Sunday, 3 February 2019 00:21:25 UTC+5:30, john wrote:
>
> I wrote something with Angular in mind. Some sample tests for Google's
> angular components are here:
>
>
> https://github.com/jfitisoff/insite/blob/master/spec/material_angular_io_spec.rb
>
> And
Hi Titus,
Is it possible to automate AngularJs application using WATIR? Any gem is
available?
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before you ask, be nice.
HI, I have resolved all the problem I have given above, I have download the
ffmeg binary and placed it in bin
but now it's throwing this error
Traceback (most recent call last):
3: from Example.rb:22:in `'
2: from
Hi, Here is the screenshot
On Sunday, 3 February 2019 15:29:06 UTC+5:30, Lakshya Kapoor wrote:
>
> Can you run "ffmpeg" in CMD and share what you get back? That error means
> ffmpeg is not found. Also, it would be helpfulif you can create an Issue on
> GitHub. We're going off-topic from the
Yupiii! Yes, it's recording. It's awesome Dude. But would it work for
Chrome as well? I tried for chrome as well, but it's not working. Is it
only for firefox?
On Sunday, 3 February 2019 15:43:08 UTC+5:30, Lakshya Kapoor wrote:
>
> Here is how you can add the ffmpeg location to PATH -
>
Oh I could install the gem using the following command
gem install ffmpeg-screenrecorder --pre
On Saturday, 2 February 2019 03:02:21 UTC+5:30, Lakshya Kapoor wrote:
>
> Awesome! You can checkout some example code and a demo here -
>
Hi when I try to install the gem `ffmpeg-screenrecorder`
I got the following error. Anything should I need correct? Or gem name
changed?
C:\Users\rajagopalan.m>gem install ffmpeg-screenrecorder
ERROR: Could not find a valid gem 'ffmpeg-screenrecorder' (>= 0) in any
repository
On Saturday, 2
Hi when I try to install the gem gem install ffmpeg-screenrecorder
C:\Users\rajagopalan.m>gem install ffmpeg-screenrecorder
ERROR: Could not find a valid gem 'ffmpeg-screenrecorder' (>= 0) in any
repository
ERROR: Possible alternatives: screen_recorder, message-recorder
So should I have to
After I have installed the gem, I started running with
require 'ffmpeg-screenrecorder'
And it throws the following error
C:\Ruby25\bin\ruby.exe Example.rb
INFO: Could not find files for the given pattern(s).
Traceback (most recent call last):
2: from Example.rb:12:in `'
1:
HI, I have already tried typing that on cmd, it's throwing the same error.
Can you please let me know how to set this file in path? I have set the
environmental variable `C:\Ruby\bin` where I placed this ffmpeg file.
On Sunday, 3 February 2019 15:29:06 UTC+5:30, Lakshya Kapoor wrote:
>
> Can
Yes, It's done now. and it's recording the video, but in video nothing
seems to be appearing. Video runs and only video name appears. Nothing
else. I ran your program
require 'watir'
@browser = Watir::Browser.new :firefox
# FFMPEG::WindowTitles.fetch('firefox') # Provide name of exe
#=>
HI, I have done something wrong, your recorder is picking up the first
opened window. and that's the reason I found some problem because I have
already opened few other windows. So it's running for firefox fine now. But
it's not recording for Chrome. Will it work for Chrome?
On Sunday, 3
Hi, Out of ten, it recorded properly only 2 times. Rest of the time, it
displays the black colour screen and in the middle file name appears while
video moves on
this is what appears
On Sunday, 3 February 2019 15:43:08 UTC+5:30, Lakshya Kapoor wrote:
>
> Here is how you can add the ffmpeg
Hi Titus,
Can I use Ruby 2.6? WATIR is supported with Ruby 2.6?
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before you ask, be nice.
watir-general@googlegroups.com
HI Titus,
Happy to say All my testcases are passing with Ruby 2.6.3. No problem so
far. I will inform you if I face any.
On Monday, 29 April 2019 21:37:01 UTC+5:30, Titus Fortner wrote:
>
> Yeah, I think it is something weird in our specs; I still need to track it
> down.
>
> On Monday, April
Hi,
I am getting this warning now
2019-05-02 13:57:16 WARN Selenium [DEPRECATION] Selenium::WebDriver::Error::
ObsoleteElementError is deprecated. Use Selenium::WebDriver::Error::
StaleElementReferenceError (ensure the driver supports W3C WebDriver
specification) instead.
--
--
Before
Hi Titus,
It seems like you have created a watir project for angular. Are you still
supporting to that project? Can I start working on that?
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search
96 matches
Mail list logo
