The basic structure of calling Selenium-grid is as follows:
The above is a common way to use Selenium-grid, only using its supported distributed execution function, that is, when you need to test cases more time, you can parallel to execute these use cases to shorten the overall test time; In addition, Selenium-grid supports a more friendly function , you can forward the use case to a test agent that matches the matching requirements based on the type of test that you launch in your use case. For example, if your use case specifies that you want to test the 17 version of FireFox on Liunux, the Selenium-grid automatically matches the proxy node with the FireFox17 that is registered as Linux, and if the match succeeds, forwards the test request and, if it fails, rejects the request. The code for the remote compatibility test using Selenium-grid is the same as above. The basic structure of its invocation is shown below:
Selenium grid structure diagram