Answered

Follow up questions on the Universal Selenium Runner

Stephen Akinpelumia

March 04, 2021 17:44

Hello, we recently had a demo of the Universal Selenium Runner presented at eRA and it had very good feedback on the feature. There were some questions asked that I wanted to post in the forum as follows..

1. In a scenario where the user has 5 different selenium test cases and he wishes to have them executed once on the runner, would the user have to enter the RemoteWebDriver call once in each test case?

2. In a scenario where the user has 1 selenium test case and he wishes to have it executed 3 times in the runner, would the user have to enter the RemoteWebDriver call these three times in the test case or is there a different format to specify the expected number of runs?

3. How would it work for a pool on VMs that these test cases are sent to, is the 'hub' reference in the e RemoteWebDriver call referring to the the Linux server's ip address or to one specific VM's IP Address?

4. Is there the possibility as a future enhancement to have the following features..

a. Have the ability to import a selenium test case into PROOF

b. The ability to freeform edit the content of the imported test case (JSON?).

c. Add the imported test case as part of an Execution Set used only for the Selenium Runner, in order to incorporate some/all of the great features that execution sets have (scheduling, notifications, re-runs, reporting, etc)?

Thanks.

5 comments

Rex Feizi March 04, 2021 21:01

Stephen,

Yes. Each test has its own instance of the WebDriver. This is no different than if you would run the tests locally, each test requires an instance of the web driver (i.e. session) that drives the correspondent browser.
Same as the above.
Test cases have no idea about the executors, they only know the hub (i.e. Linux server). The hub gets the request for the RemoteWebDriver, if it has free executors, it will connect the requester with the VM (i.e. executor). If there are no machines available, then there are multiple ways that this is handled. At this time, if the call to remote driver will return "Hub busy please tray again later".
A) A selenium java test cannot be imported anywhere because of many complications. For one, the test maybe using many dependent libraries and other logic inside of it. Or it could have been written in different languages like Python, C# etc. The main idea of Selenium Remote Driver is to exactly deal with this issue.
B) A Java test case is much more complicated to be represented in JSON free form, so makes no sense to do this.
C) This is not the intention of the Selenium Architecture of hub and JSON Wire Protocol.

Please take a look at https://www.lambdatest.com/blog/selenium-remotewebdriver/

Hope this helps

--Rex

Stephen Akinpelumia March 05, 2021 14:45

Thanks Rex.

Alexander (Greg) Fangonil November 18, 2021 20:25

Hi Rex,

For the way we have the Universal Runner configured, is it going to distribute the selenium tests amongst the VM pool or is it just running on the VM that the URL is pointing to?

Our goal is to see if we can leverage the Universal Runner and Proof to distribute the selenium tests amongst the VM pool so just need some clarification.

Thanks,

Greg

Rex Feizi November 18, 2021 20:31

Greg,

The URL that you are pointing to in the test script is the URL of the hub. The hub will distribute the tests amongst the VM's that are configured to be used with Universal Runner.

You can set up as many XPoint machines to be used as Universal Runner machines so you can distribute your tests.

We have plans to allow XPoint to be used both for Codeless automation (Classic proof tests) and Selenium scripts. But as of this second, you cannot share the VM's between the two.

Please let me know if this make sense and if you need more information.

Alexander (Greg) Fangonil November 19, 2021 17:44

Hi Rex - Yes, that makes sense. Definitely please let us know when XPoint can be used for both Proof and Selenium scripts so we can configure in our Test instance.

Please sign in to leave a comment.