What are the limitations of Selenium RC?
Before we answer the above question, let's understand the architecture on which the selenium RC works upon. RC uses a JavaScript Program called the Selenium core which controls the browser. It works by intimating the user action as commanded by the JavaScript commands but that does not enforce users to write automated test cases in the only JavaScript, let’s see how does RC makes that happen.
The above diagram depicts the brief architecture of the Selenium RC. (Image Courtesy:www.seleniumhq.org)
Now as it is evident that the application under test was being executed on a different system, we can say that selenium RC was dependent on the core libraries which could run on any browser which would support JavaScript.
Selenium RC has main components which are the Client libraries to develop Selenese commands which can be ported to JavaScript and then, on the other hand, it has a server that automatically launches and kills the browser as per the commands.
Below are the limitations of Selenium RC −
Selenium uses a Javascript program called the Selenium core, which directly controls the browsers. Hence there is no direct interaction with the browser, which makes it a bit slow.
Before executing any script, the server has to be restarted.
API's are less object-oriented.
Movement of the mouse cursor is not supported.
Mobile app testing is not supported.
It requires a real browser as it does not support headless HTMLUnit Browser.
Published on 04-Sep-2019 07:46:24
