Results 1 to 3 of 3

Thread: Why Selenium RC is used?

  1. #1
    Senior Member
    Join Date
    Oct 2012

    Why Selenium RC is used?

    Please explain why Selenium RC is used?

  2. #2
    Join Date
    Oct 2012
    Quote Originally Posted by Cora View Post
    Please explain why Selenium RC is used?
    The Selenium RC is used because the Selenium IDE does not directly support the following:

    1. condition statements,

    2. iteration,

    3. logging and reporting of test results,

    4. error handling, particularly unexpected errors,

    5. database testing,

    6. test case grouping,

    7. re-execution of failed tests,

    8. test case dependency and

    9. capture screenshots on test failures.

    The reason behind why Selenium-IDE does not support the above mentioned requirements is IDE supports only HTML language. Using HTML language we cannot achieve the above mentioned requirements. Because HTML does not support conditional, looping and external source connectives.

    To overcome the above mentioned problems Selenium RC is used.
    Since Selenium RC supports the languages .Net, Java, Perl, Python, PHP, and Ruby. In these languages we can write the programme to achieve the IDE issues

  3. #3
    Junior Member
    Join Date
    Nov 2015
    Selenium Remote Control (RC) is a server, written in Java, that accepts commands for the browser via HTTP. RC makes it possible to write automated tests for a web application in any programming language, which allows for better integration of Selenium in existing unit test frameworks. To make writing tests easier, Selenium project currently provides client drivers for PHP, Python, Ruby, .NET, Perl and Java. The Java driver can also be used with JavaScript (via the Rhino engine). A new instance of selenium RC server is needed to launch html test case - which means that the port should be different for each parallel run.[citation needed] However, for Java/PHP test case only one Selenium RC instance needs to be running continuously.[citation needed]

    Selenium Remote Control was a refactoring of Driven Selenium or Selenium B designed by Paul Hammant, credited with Jason as co-creator of Selenium. The original version directly launched a process for the browser in question, from the test language of Java, .Net, Python or Ruby. The wire protocol (called 'Selenese' in its day) was reimplemented in each language port. After the refactor by Dan Fabulich, and Nelson Sproul (with help from Pat Lightbody) there was an intermediate daemon process between the driving test script, and the browser. The benefits included the ability to drive remote browsers, and the reduced need to port every line of code to an increasingly growing set of languages. Selenium Remote Control completely took over from the Driven Selenium code-line in 2006. The browser pattern for 'Driven'/'B' and 'RC' was response/request, which subsequently became known as Comet.

Similar Threads

  1. Replies: 1
    Last Post: 11-02-2012, 06:51 AM
  2. Replies: 1
    Last Post: 11-02-2012, 06:49 AM
  3. Selenium RC
    By Sanvi in forum Selenium
    Replies: 1
    Last Post: 11-01-2012, 11:34 AM
  4. Replies: 1
    Last Post: 11-01-2012, 11:25 AM
  5. What is Selenium RC?
    By Cora in forum Selenium
    Replies: 1
    Last Post: 10-31-2012, 08:54 AM


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts