{"id":55601,"date":"2022-09-30T15:56:33","date_gmt":"2022-09-30T10:26:33","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=55601"},"modified":"2022-09-30T17:09:25","modified_gmt":"2022-09-30T11:39:25","slug":"understanding-the-new-selenium-grid-4","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/understanding-the-new-selenium-grid-4\/","title":{"rendered":"Understanding the Selenium Grid 4"},"content":{"rendered":"

Selenium Grid is an open-source tool to automate web browsers. It allows us to achieve parallel execution of tests on different machines with the benefit of executing the same test suite on all the machines simultaneously. <\/span>The aim is to make testing more efficient and decrease the test execution time. It also aids in lessening network traffic by distributing requests amongst all servers.<\/span><\/p>\n

Selenium Grid can be primarily used for cross-browser testing, cross-platform testing, and cross-browser compatibility testing. It can be used for functional and non-functional testing. <\/span>It can also be used for performance testing of any web application.<\/span><\/p>\n

Components of SELENIUM GRID<\/b><\/p>\n

\"\"<\/p>\n

1. D<\/b>istributor<\/b><\/p>\n

It is liable to register and keep track of all Nodes and their capabilities. It is used to query the New Session Queue and then process pending new session requests<\/span><\/p>\n

2. Session Map<\/b><\/p>\n

It is used to maintain a mapping between the session ID and the address of the Node on which the session is running.<\/span><\/p>\n

3. Router<\/b><\/p>\n

It acts as the entry point for the Grid. It is an integral part of the Grid which can<\/span> be exposed to the wider Web. It can receive all external requests, and send them to the correct component, without overburdening any component which is not needed in the process.<\/span><\/p>\n

4. Hub<\/b><\/p>\n

The hub is the centrist point where tests are loaded into. There is only one hub in a grid. It can be launched in a single machine only.\u00a0<\/span><\/p>\n

5. Nodes<\/b><\/p>\n

Selenium instances are used to execute the tests loaded in the hub. There can be more than one node in a grid. Nodes can launch on several machines with multiple platforms and browsers.<\/span><\/p>\n

6. Session Queue<\/b><\/p>\n

The New Session Queue adheres to the FIFO ordering for all the new sessions which are requested. It consists of configurable parameters in order to set up the request retry interval. and request a timeout.<\/span><\/p>\n

7. Event Bus<\/b><\/p>\n

The Event Bus works as a communication path between the Distributor, Nodes, Session Map, and New Session Queue. The Grid performs most of its internal communication by avoiding expensive HTTP calls and messages.<\/span><\/p>\n

Selenium Grid 3 vs Selenium Grid 4<\/b><\/h2>\n

\"\"<\/p>\n

Different Grid Types<\/b><\/h2>\n

Previously in Selenium Grid version 3, only Hub and Node(s) were used. Selenium 4 has some new updated and advanced features including two more types of Grid. Below mentioned are the three grid types supported in Selenium 4:<\/span><\/p>\n

1. Standalone Mode\u00a0<\/b><\/p>\n

In the Standalone mode, the Selenium server executes everything in-process. Standalone is a union of all the components of Selenium Grid. If we want to run Hub and Node on the same machine, we can use this mode. It is invoked by running the below-mentioned command on the terminal ->\u00a0<\/span><\/p>\n

java -jar selenium-server-4.4.0.jar standalone<\/span><\/pre>\n
The Grid automatically analyzes the WebDrivers for Chrome and Firefox that are present on the system.<\/span><\/p>\n
The server is listening on http:\/\/localhost:4444\/ which is the same address used in the configuration of the Remote WebDriver. <\/span>The Chrome WebDriver is only registered once the test code is executed.<\/span><\/p>\n
2. Hub and Node Grid<\/b><\/p>\n
This is the traditional technique to use the Grid for Selenium test automation that consists of two major components \u2013 Hub and Nodes<\/span><\/p>\n
Hub is the amalgamation of the following components:<\/p>\n
    \n
  • \n
      \n
    • Router<\/li>\n
    • Distributor<\/li>\n
    • Event Bus<\/li>\n
    • New Session Queue<\/li>\n
    • Session Map\n
      <\/b><\/li>\n<\/ul>\n<\/li>\n
    • \u00a0Starting Hub in the machine using:<\/span><\/li>\n<\/ul>\n
      java -jar selenium-server-4.0.0.jar hub <\/span><\/pre>\n
        \n
      • A node having the same machine
        \n<\/span><\/p>\n
        java -jar selenium-server-4.4.0.jar node<\/span><\/pre>\n<\/li>\n
      • A node having a different machine
        \n<\/span><\/p>\n
        java -jar selenium-server-4.4.0.jar node --detect-drivers <\/span>true<\/b> --publish-events tcp:\/\/{hubIP}:4442 --subscribe-events tcp:\/\/{hubIP}:4443<\/span><\/pre>\n<\/li>\n
      • hubIP – Displayed in the cmd logs on registering the hub<\/span><\/li>\n<\/ul>\n
        3. Fully Distributed\u00a0<\/b><\/p>\n
        It can perform in a fully distributed manner, with each piece executing its procedure. In this approach, we have to kickstart all the components individually like Router, Distributor, and more. It is used when we have a larger size Grid to be set up.<\/span><\/p>\n
          \n
        • \u00a0Session Map<\/strong>\n
            \n
          • Maps the Session Ids for the executing node sessions<\/span><\/li>\n
          • Kickstart the Session Map with the help of the below-mentioned command:
            \n<\/span>
            \n<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
            java -jar selenium-server-4.4.0.jar sessions<\/span><\/pre>\n
              \n
            • \n
                \n
              • It maps the Session IDs to the node the session is presently running on<\/span><\/span> <\/li>\n<\/ul>\n<\/li>\n
              • Event Bus<\/strong>\n
                  \n
                • It will be used to communicate between different components of the Grid<\/span><\/li>\n
                • Start the Events Bus using the below-mentioned command:
                  \n<\/span><\/p>\n
                  java -jar selenium-server-4.4.0.jar event-bus<\/span><\/pre>\n<\/li>\n<\/ul>\n<\/li>\n
                • Session Queue<\/strong>\n
                    \n
                  • Appends the new session requests to a queue<\/span><\/li>\n
                  • This queue will be refined by the distributor later<\/span><\/li>\n
                  • Start the Session Queue using the below-mentioned command:
                    \n<\/span><\/p>\n
                    java -jar selenium-server-4.4.0.jar session queue\r\n<\/span><\/pre>\n<\/li>\n<\/ul>\n<\/li>\n
                  • Distributor<\/strong>\n
                      \n
                    • Nodes inscribe to this Distributor<\/span><\/li>\n
                    • The distributor verifies the Session Queue and then assigns the new sessions to the inscribed node which is accessible to run the sessions<\/span><\/li>\n
                    • Start the Distributor using the below-mentioned command:
                      \n<\/span><\/p>\n
                      java -jar selenium-server-4.4.0.jar distributor --sessions http:\/\/192.168.0.112:5556 --sessionqueue http:\/\/192.168.0.112:5559 --bind-bus false\r\n<\/span><\/pre>\n<\/li>\n<\/ul>\n<\/li>\n
                    • Router<\/strong>\n
                        \n
                      • Navigates the requests to accurate components<\/span><\/li>\n
                      • The entry point of Grid<\/span><\/li>\n
                      • Start the Router using the below-mentioned command:
                        \n<\/span><\/p>\n
                        java -jar selenium-server-4.4.0.jar router --sessions http:\/\/192.168.0.112:5556 --distributor http:\/\/192.168.0.112:5553 --sessionqueue http:\/\/192.168.0.112:5559\r\n<\/span><\/pre>\n<\/li>\n<\/ul>\n<\/li>\n
                      • Node<\/strong>\n
                          \n
                        • Start node in the same machine:
                          \n<\/span><\/p>\n
                          java -jar selenium-server-4.4.0.jar node<\/span><\/pre>\n<\/li>\n
                        • Start node in a different machine:
                          \n<\/span><\/p>\n
                          java -jar selenium-server-4.4.0.jar node --detect-drivers true --publish-events tcp:\/\/192.168.0.112:4442 --subscribe-events tcp:\/\/192.168.0.112:4443<\/span><\/pre>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n

                          \nAdvantages of Selenium Grid<\/b><\/h2>\n
                            \n
                          1. Open Browser: Selenium is an open source and easily accessible automation framework having no upfront costs. So, users can save lots of money here and utilize them for other good reasons.<\/span><\/li>\n
                          2. Support Multiple Browsers: Firefox, Chrome, IE, etc.\u00a0<\/span><\/li>\n
                          3. Support Multiple Architecture and OS: Windows, Linux, UNIX, Mac OS, etc.<\/span><\/li>\n
                          4. Escalates Test Execution Time: It boosts up the completion time of the test suite as it can execute multiple tests in parallel. For instance, if we have 5 nodes and we want to run a test suite of 60 tests then it will take 6 times less time than a single machine that runs the same test suite without Selenium Grid. When a node is idle, it picks up the test case waiting in the execution queue on its own.<\/span><\/li>\n
                          5. Execution of Cloud Based: Reliability, Availability, Software Maintenance Cost, and Save Hardware.<\/span><\/li>\n
                          6. Framework and Language Support: It holds up all crucial languages like Java, C#, Python, JavaScript, Perl, Ruby, and programming languages for software test automation.<\/span><\/li>\n<\/ol>\n

                            \nDisadvantages of Selenium Grid<\/b><\/h2>\n
                              \n
                            1. Cost: Additional cost for the project as it needs extra machines as Nodes.<\/span><\/li>\n
                            2. Poor Scalability: It has comparatively poor scalability as compared to many present-day applications. It is inadequate to increase or decrease demand.\u00a0<\/span><\/li>\n
                            3. Reconfiguration: It is static. Each server is customized beforehand with a subset of the needed browser instances available. If you want to differ this, you have to reconfigure it.<\/span><\/li>\n
                            4. Need skilled engineers: Selenium Grid requires skilled engineers to create and maintain things and IT approval.\u00a0<\/span><\/li>\n<\/ol>\n

                              \nSummary<\/b><\/h2>\n
                              At last, we can say that It will increase the marketing strategy for the big growing companies in the coming future. It is having wide scope in regards to growing Industry standards. It assists with the deployment of non-defective code. A Grid contains a single Hub and one or more Nodes. Both can be used with the help of a selenium-server.jar executable. The Hub receives a test that needs to be run along with detailed information on which browser(Firefox, chrome) and platform (i.e. Windows, Linux\/Unix, etc) where the test should be executed. Since the Hub is aware of each registered Node and its configurations, it picks up any available Node which contains a\u00a0 browser-platform combination that is already requested.<\/span><\/p>\n
                              <\/div>","protected":false},"excerpt":{"rendered":"
                              Selenium Grid is an open-source tool to automate web browsers. It allows us to achieve parallel execution of tests on different machines with the benefit of executing the same test suite on all the machines simultaneously. The aim is to make testing more efficient and decrease the test execution time. It also aids in lessening […]<\/p>\n","protected":false},"author":1408,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":37},"categories":[1816],"tags":[14,25,2857],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/55601"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/1408"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=55601"}],"version-history":[{"count":4,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/55601\/revisions"}],"predecessor-version":[{"id":55650,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/55601\/revisions\/55650"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=55601"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=55601"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=55601"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}