What I am getting at: Is testing the chrome-browser via these docker images exactly equivalent to testing it in a normal environment where the browser has it's normal GUI? Or is it emulated in some way?
--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-users+unsubscribe@googlegroups.com.
To post to this group, send email to selenium-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/6e86242f-323d-4077-8b2a-cc00dcd18cfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>>>>>> So as far as I understood, using these docker-images I can already test Chrome and Firefox (and optionally phantomJS) perfectly fine in a headless environment (such as the Jenkins) - correct? Apart from some limiations (bugtracker suggests that some video playback might not work, etc.) everything else should work just as if the server was running on an actual server with UI?
Yes, that is correct. Although I don’t know about the validity of the bug that you talk about, mainly because I haven’t dirtied my hands yet in this arena ☺
>>>>>> Now, what about the Internet Explorer? As far as I can see there is no image for the IE - I assume that is because of limiations that the browser itself forces onto the underlying driver. Most likely some amount of issues regarding the usage of xvfb, I assume?
IE doesn’t have a docker image because all docker images are LINUX based and there’s no way of running a windows based IE browser on LINUX. I have heard that Microsoft is also going to be coming out with windows docker images (on top of their windows server OS), but until that happens, you are stuck with using a physical/VM to run your IE based tests. It has got nothing to do with xvfb
>>>>>> I suppose that to test the IE I will need a dedicated server with UI. I guess it should be possible to add such node to the dockerized hub (which would already have the chrome-node container and the firefox-node container registered)?
The docker hub is just like running a hub on a physical/VM. So yes, I think you should be able to wire in a node that is running on a windows machine, to the hub that is running within a docker container. You may have to take care of resolving the network nuances though (if they occur). What would those nuances be, well, I don’t know. My networking skills aren’t that strong ☺ But feel free to post back on this forum and someone am sure will help you out with your query.
Thanks & Regards
Krishnan Mahadevan
"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/
My Technical Scribbings @ http://rationaleemotions.wordpress.com/
--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To post to this group, send email to seleniu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/fbb61547-baec-42cc-bbf5-231d9080df9c%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-users+unsubscribe@googlegroups.com.
To post to this group, send email to selenium-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/81eef799-69eb-458b-8f83-e3f3205ca537%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-users+unsubscribe@googlegroups.com.
To post to this group, send email to selenium-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/aa6970cf-c7bf-4e0c-b09a-40dd2a5fc405%40googlegroups.com.