Selenium Remote Control

The pre-requisites to run Selenium RC tests with Junit:

1) Jre 1.5 or better version needs to be installed

2) /jre/bin folder must be added in environment variable "path"

3) Junit folder path must be added to path or build path in eclipse

4) Selenium Java Client drivers needs to be added to the path for execution

You can run the selenium commands in RC slow motion by two ways:

selenium.setSpeed

thread.sleep

The procedure followed to run the Selenium RC Server is:

1. Open the command prompt.

2. Change the folder path to Selenium RC Server

3. Issue the command "java -jar selenium-server.jar"

1) Download eclipse.

2) Open eclipse -> Workspace Launcher window will open

3) Create a workspace by giving meaningful name

3) Click on Workbench

4) Create a project of type java

5) Create a package under src folder of the package

6) Add Junit to the build path

7) Add selenium rc java client driver to the build path

8) Now drag and drop your test script (.which is exported from Selenium IDE) to the package created

selenium.setSpeed

1. takes a single argument in string format

ex: selenium.setSpeed("2000") - will wait for 2 seconds

2. Runs each command in after setSpeed delay by the number of milliseconds mentioned in setSpeed.

thread.sleep

1. takes a single argument in integer format

ex: thread.sleep(2000) - will wait for 2 seconds

2. Waits for only once at the command given at sleep.

SeleneseTestCase is the class which is having

1. assertTrue

2. verifyTrue

3. assertEquals

4. verifyEquals

We use SeleneseTestCase class to extend the selenium test class file.

For Ex: the test class is declared as follows

public class BookFlightSel1 extends SeleneseTestCase

In the above example SeleneseTestCase is the base class and BookFlightSel1 is the derived class. So, we can directly call and use the parent class methods verify and assert without instantiating the class in BookFlightSel1 class.

The annotations generated with JUnit 4 tests in Selenium are:

1. @Before public void method() - Will perform the method() before each test. This method can prepare the test

2. @Test public void method() - Annotation @Test identifies that this method is a test method.environment, e.g. read input data, initialize the class)

3. @After public void method() - Test method must start with test@Before - this annotation is used for executing a method before.

The challenges with Selenium RC test suites when running in JUnit

1. Each test case of Selenium RC test will invoke the browser and closes after playing back

2. All the Test cases cannot run on a single browser session

3. If there is any dependency between the test cases, it is very difficult to execute

4. Running the test suites in junit will be helpful for only independent test cases.

Note: The dependent test case related issues can be addressed by using TestNG with junit

The basic annotations used to run TestNG tests in Selenium RC:

1. @BeforeClass: The annotated method with @BeforeClass will be run before the first test method in the current class is invoked.

2. @AfterClass: The annotated method with @AfterClass will be run after all the test methods in the current class have been run.

3. @BeforeMethod: The annotated method with @BeforeMethod will be run before each test method.

4. @AfterMethod: The annotated method with @AfterMethod will be run after each test method.

5. @Test: Marks a class or a method @Test with as part of the test.

The @Test should be followed by (dependsOnMethods = "testLogin")

Note:- The test case will be executed after the testLogin case

Ex: @Test(dependsOnMethods = "testLogin")

Test cases in group in Selenium using TestNG will be executed with the below options.

If you want to execute the test cases based on one of the group like regressiontest or smoketest

@Test(groups = {"regressiontest", "smoketest"})

to run Selenium IDE test suite with user extensions using Selenium Remote Control we need to use the below command.

java -jar selenium-server.jar -userExtensions user-extensions.js -htmlSuite "*<browser>" "<base URL>" "<Selenium test suite file>" "<results log file>" -timeout <millise>

The limitations of selenium RC are:

1) Switching between the multiple instances of the same browser is not possible

2) Switching between the multiple instances of the different browsers is not possible

3) Browser navigation, like back and forward button emulations is not possible

4) Limited features in terms of drag and drop of objects

5) To work with Ajax based UI elements there are very limited features are there with Selenium RC

To overcome the above limitations we use selenium web driver or google web driver

The command used is

java -jar selenium-server.jar -userExtensions user-extensions.js

Note: In this case, the java script file user-extensions.js file name should always fixed. If the name or extension is changed the selenium rc server will not start.