#selenium

^^

:)

Just ask selbot3

heh.

I did find a couple of Java options so that I could hide the GridLauncher (and v3) "wrapper" Java applications from potentially stealing focus of the browser, but that didn't actually change the results of our tests at all

We don't talk about selbot3...

Dark times

What's interesting is that we were still supporting SE 2.x with the old SafariDriver extension on Safari 10, and it seems to get this error maybe 25% of the time we launch a test, whereas using 3.x with both Safari 10 and 11 we get this exception way more frequently

tim-sl: that's interesting, because in both cases you should only be using the 2.x code paths

I realize SE2.x, the SE Safari Extension and Safari >= 10 is not officially supported, right?

not only not officially, not likely to work at all

tim-sl: right

Hehe, it does seem to "work" besides this weird issue

And that's true, the GridLauncherv3 app would only show up when we're using the newer Apple-maintained driver

And SE3

And.. please excuse my noobness here, I'm pretty new to Selenium and the different browser drivers.

I guess I'm wondering if such an error reported by the driver could be due to something graphics-related in our VM environment, and a different in how Safari behaves in it

My first step was to try and repro it in something consumable by someone who helps maintain these projects, but not being able to do that yet leaves me trying to play detective

tim-sl: Have you tried running Java with AWT headless mode enabled?

`java -Djava.awt.headless=true -jar selenium-server-standalone-3.7.1.jar`

Yeah, I've tried both just `java.awt.headless=true` and also `apple.awt.UIElement=true`

And?

Did it help?

Gridlauncher and the Java app wrapper no longer show up and are visible in any way, but the consistency of the errors about the window availability are the same

Well, I guess that doesn't help much. Damn it

I thought it would :)

Yeah, I was hoping it would too.

That's where I figured that maybe people who work with SafariDriver on a regular basis have noticed some conditions under which this could happen

brrian might know

I'm not sure. Sorry

No problem, thanks! Hopefully brrian may be able to point me in the right direction at least.

If I install the Safari TP right before we kick off a test, is there any other configuration required on the system?

You need to enable it in the SafariOptions

`new SafariOptions().setUseTechnologyPreview(true)`

ok, thanks :)

[13selenium] 15jimevans pushed 11 new commits to 06master: 02https://git.io/vbUqx

13selenium/06master 14034519f 15Jim Evans: Updating IE driver element tag name command handler to be spec compliant

13selenium/06master 14406b8da 15Jim Evans: Return NoSuchElement error in IE with incorrect internal IDs...

13selenium/06master 148d73e5f 15Jim Evans: Making IE driver SetWindowRect command compliant with spec

okay. that's the IE driver stuff that's been fixed for spec compliance.

jimevans: The diclaimer has been added to chocolatey package: https://chocolatey.org/packages/selenium. Let me know if there is anything else needed to be compliant.

that should say “disclaimer"

does anyone get hung commands with selenium grid 3.7.1 (using a client that doesn't set an HTTP timeout)

Hello , I am running my selenium tests in docker selenium hub because of some wait time in my test the docker VM's are getting closed (I am guessing this is due to browser is idle) is there any setting in docker that i need to make such that the docker vm's should not close due to any inactivity of the browser ?

it's generally a setting in the selenium server

i beleive the default is 90 seconds timeout if no commands are received

@dude-x Can we increase this time from 90 seconds ?

Darn it.

I want to use a CapabilityTransform on the OSS capabilities

jimevans: we can postpone 3.8 till you land the commits sitting in the queue, there is no hurry

barancev: they just landed.

oh, nice!

let me update the changelog for .NET

okay, .NET is updated, and ready to go at your pleasure.

[13selenium] 15jimevans pushed 1 new commit to 06master: 02https://git.io/vbUsZ

13selenium/06master 14d897de9 15Jim Evans: Updating .NET CHANGELOG and version resources for impending 3.8 release

Hello All , Is there any option where i can change the default wait time from 90 sec in docker when no command received from selenium tests due to large wait times ?

g'day

[13selenium] 15barancev pushed 2 new commits to 06master: 02https://git.io/vbUB0

13selenium/06master 145844316 15Alexei Barantsev: Updating Java changelog for 3.8

13selenium/06master 1457fe003 15Alexei Barantsev: Bump version number to 3.8

[13selenium] 15barancev tagged 06selenium-3.8.0 at 06master: 02https://git.io/vbUBw