#selenium

and it doesnt update

it is updating though

each time the button is clicked i do html = driver.page_source

which updates it

but that doesnt update it :-P

when you hit the next button, the actual page doesnt change, just the content in the table

driver.page_source doesnt change when you change pages

i just tried it with a text compare

unless it changed recently..

@lucast is it intentional that Ruby bindings no longer support: `Remote::Capabilities.firefox(firefox_options: {binary: ENV['ALT_FIREFOX_BINARY']})`

going to have to ask alex on that

it works with new FirefoxOptions implementation

he integrated the classes

but it isn't deprecated just ignores it

ok

I'll PR and ask

thought you might have had a hand in that

i created the classes but he did a bunch of changes to implement them and i havent looked at anything really since slightly before that unfortunately :(

simonstewart: note from jimevans about 2 hours ago: i'll take a look, but i don't know what kind of connectivity i'm going to have tomorrow or the next day.

lucast: it seems to be updating for me in my python script, i am able to scrape all content from subsequent pages from the table

FuZi0N: cool, i wonder if chromedriver changed something then

let me try with chrome now

i was using firefox

oh

hey, if it works, it works :)

;)

works with chrome for me as well

jimevans: are you in Japan yet?

hmm, mac specs are broken in Ruby; haven't run them in forever so I have no idea if we broke something or Apple did :)

AutomatedTester: not yet. leave tomorrow morning.

hi, trying hard to bring selenium tests in our jenkins pipeline..possibly without saucelabs and selenium server...using selenium/firefox container

this really should be in introductions

:)

but anyway..our test engineer delivered me locally executable firefox selenium tests

to put it in our jenkins pipeline

so i pulled the selenium/firefox container

changed the code to use remote localhost:4444 firefox driver

but from some reason the firefox inside the container doesnt find our test server where the webapp is deployed to be tested at all times

[13selenium] 15titusfortner opened pull request #4238: [rb] log error when using :firefox_options in Remote::Capabilities (06master...06rb_ff_opts) 02https://git.io/vQW35

https://wiki.mozilla.org/Releases | Every version of Firefox can be found here http://ftp.mozilla.org/pub/mozilla.org/firefox/...

tried to exec in container to try to reach our test server from inside selenium container (curl, ping) but there are no such commands are thez

so its not a public webapp like google, it is on our intranet

and when i run tests locally they execute...just not from container

the containers dont have curl?

how are you instantiating your browser in your code?

and which container are you using? selenium/node-firefox, selenium/standalone-firefox?

@channel - Need some help to find alternative to Thread.sleep in cases when the same page reloads and none of the expected conditions of WebDriverwait helps. What to look for when the page reloads ?

oh boy here we go

You need to use ExpectedCondition class

i'd laugh if i didnt have a slack account as well...

ohai lucast….

i have just tried elenium/standalone-firefox-debug

meena-sl: how is it that none of the expected conditions work?

and vnced

inside

and i can get google.com

inside browser

but not our local intranet

maybe your local environment has special DNS setup that isnt translated to the container? i'm not sure how all that works

@lukeis-sl: -_-

indeed

meena-sl just a first thought… does the page always reload? you could wait for an element to no longer exist on the page then just continue as selenium won’t interact with a page mid load

andrejpodgors-sl sounds like external problem , now sysadmin rocks

lukeis.. i thought you were banned from slack... if i recall correctly, you had a less-than-tolerable name LOL

slack didnt care about his name, but freenode did :-P

i made it more tolerable ;)

err, consistent with my other slack instance

:indeed:

success ;)

huh? you didnt just use the same old username for your work one too?

meena: just a first thought… does the page always reload? you could wait for an element to no longer exist on the page then just continue as selenium won’t interact with a page mid load

:success:

jordancw418-sl: just an fyi, the #selenium channel is relayed to IRC and threads do not translate well in that aspect

ahh thanks

need to add that to the doc on the side...

shit man

you were right

with ip i get through...dns is funny

and u know why...

lucast waiting for custom emoji to bite us ;)

because i changed it to 8.8.8.8 in docker networking settings

from auto

jordancw418-sl Yes the page always reloads ...everything remains same after the page reload ..so even if i wait for visibility of element again that returns true...

because docker pull wasnt working

:fu: heh

it timed out

like 4/5 hours ago

lol

so if the element disappears you might be able to catch that by waiting for num elements to be 0 then just trying to interact with the element again

such great emoji from slack

i feel like i ought to go out and get shitfaced...

no element do not disappear totally the same page reloads

Please don't use @ channel. It is not good to use.

alright… it’s been real fun saying hi for 2 minutes… now back to the work conference…

we will summon you via red dot if necessary

:+1:

oh dang, then I don’t know what else to tell you… if the html doesn’t refresh completely then my solution won’t work… without seeing it firsthand idk

is it an angular app? maybe protractor will handle this for you

smccarthy-sl - Got that i have been using other channels so may be out of habit...Will take care of it next time.

not an angular app

meena-sl: probably fine to use in smaller channels, but not ones with 800+ people

right, you generate notifications to a lot of people, such as the email i just got

:-P

you'd think the "Are you sure you want to send this message to 822 members in 18 time zones?" warning would deter people

it says that?

yup

every time you at channel

interesting...

pffft, people don't read warning messages

so, I have a very low tolerance for people plowing ahead anyway

"my question is more important than the time wasted by the 815 people not actively reading right now"

[13www.seleniumhq.org] 15tourdedave pushed 1 new commit to 06master: 02https://git.io/vQW8f

13www.seleniumhq.org/06master 1412938ff 15Dave Haeffner: Updated tophat promo for SeleniumConf Berlin Standard tickets

right, meena-sl, so assume you have a reference to an element, and you need to find the same element (with an identical locator) when the page refreshes.

assuming it's a real, honest-to-{$deity} page refresh, you can use the stalenessOf expected condition to signal that the page has at least begun its reload

then search again for the element.

which will be guaranteed to be a new (after the page refresh) instance of the element