#selenium

For a newbie, is there a good place or document to use to get started? The Selenium web site is rather confusing. Goal is to test IE and Chrome.

seems like it died at 1-2am last night

not even died, just quit normally

I found the api docs very useful

for the python driver anyway

CTtpollard: if only we could link them :P

*shakes fist at lukeis*

probably moved his desk again

or had to -gasp- switch his pc off

thanks CTtpollard, I will look at them

hmm, I've jsut become aware of how overly-reliant I am on that bot… I actually don't know where the docs are!

Dave_B_: me either :p

how does grid distribute tests among nodes?

say i have 2 modes with 4 browser slots each

does it do round robbin?

it'll take all 4 fro mne node before hitting the other

round robin I think

unless this has changed, certainly used to just take first free browser which was ordered by node

right, it'll take the first free browser

so its essentially round robin

dimacus: ^

huh?

one sec

*chants* We! Want! Sel! Bot!

*looks at lukeis*

ohai

:p

Dave_B_: ok so this is how the grid would take nodes before my PR earlier this week

1) Collect all the set of all nodes, 2) sort by some default java Collection.sort call, 3) try to start a new session on each node in the "sorted" set until the first node picks up and says "here you go"

my PR did a minor change to the Collection.sort, where it just changed step 2), and sorted all of the nodes by how busy they are, idle ones go on top, busy ones on the bottom (totalUsedSlots / totalCapacipty)

WhereIsMySpoon: is your life complete again? ;)

and yes… i moved desks *again*

lukeis: I thought as much :p

10th desk in 4.5 years ;)

and yes ;)

:api

.NET: http://goo.gl/uutZjZ | Java: http://goo.gl/Grc6tm | Ruby: http://goo.gl/jzh4RU | Python: http://goo.gl/sG1GfQ | Javascript: http://goo.gl/hohAut

Dave_B_: it's not round robin per se… so some nodes will pick up more builds over and over right now, but at the very least, if there is a node that is idle while one is running 2 tests, the idle has a higher chance of picking up new build

ODA_AG: ^

i guess its kinda like a greedy round robin

at the moment

dimacus: that sounds a lot better now with your patch.

dude-x, WhereIsMySpoon: I got to the bottom of my event questions. It all comes down to the value of event.isTrusted, which is set to true for any event being initiated via webdriver synthetic events, but set to false when injecting js events directly on the page

yea

Thanks WhereIsMySpoon!

brma: sounds like a reasonable explanation

brma: ah interesting; your element has side effects when webdriver clicks it

glad you got it sorted

My SUT cares abut this value, yes. Thanks guys

dude-x: I'd imagine some sort of pop-up appears when he clicks his input or similar

dude-x: it's not perfect but yes it's an improvment… i've been watching 1 grid's logs in particular. The issue would be, there are 20 nodes 18 of which were 100% idle and 2 of them would be running 2 or 3 instances of chrome builds at the same time… as of the PR the load is spread thinly across all nodes, at any given point 5 to 15 of them are running 1 build each

nice :)

alright folks i need lunch, cheers

o7

ciao

dude-x: hey, is appium working again for you?

i haven't upgraded to 2.47 yet, but based on the changes it should work ...

oh, 2.47 is out?

i am currently running a test now... I will try it on the next test run

*looks at channel topic*

yea 2.47 supports Edge and W3C specific stuff (marionette support for firefox)

channel topic needs updating then :p

Hopefully it won't be W3C specific for too long, so it can become “WebDriver general”. (-:

woop that worked

ato: ++

AutomatedTester: 2.47 ;)

close

lol

But close enough?

Oh AutomatedTester just said “bbl” in another channel.

heh

yay

lukeis: also, the second logs link is not really up to date

last update 4 mo ago

WhereIsMySpoon: but it has "history"

maybe put (historical) ?

i'm ok with getting rid of it… people who really care can find it

yea

most people just want to look at the logs for the previous hours or day anyway

not years

oh my running an appium test is making the fans spin on my mac book pro.

they get pretty noisy

hmmm iTerm 3 is using 1.5GB of ram. <checks scrollback setting. sees Infinite SCrollback enabled.> I see...

jimevans: so… i guess i need to make a "edge-driver" maven package :-/

especially since it got defaulted to the 'leg-rc' package… heh

Is there any reason to use marionette if I don't need to interact with Firefox's browser chrome?

your chances of getting "native" interaction are much higher if you use marionette… plus it is "the future" but i don't believe it's a substitute for FirefoxDriver yet

is that how you see marionette?

I'm not sure how to see it, I guess.

more native events are a good thing though

when "shopping around" for a new manager and the new manager wants to talk to you while they are on vacation… I take that as a bad sign ;)

office politics?

dude-x: my previous manager left the company last week and there is no intention to re-fill the position. Rather just shuffle my team around

AutomatedTester: confirmed that I have no issue with 2.47.0 using appium

brma: In addition to what lukeis said, FirefoxDriver will eventually break because it doesn't support multi-processed Firefox.

brma: Right now, however, Marionette does not have parity with FirefoxDriver in terms of compatibility and features.

lukeis: did i put the edge driver pieces in the wrong package?

do brits use the word 'tiffin'