Skip to main content

Selenium Tutorial: Selenium Grid 1.0 configuration

I must say I did not have an easy time trying to set up Selenium Grid 1.0 locally. Since I did not have access to multiple machines I was trying to setup hub as well as slave remote control and was following the doc available here. Though documentation is detailed it is tough to have it replicated with your set up. of late I posted about ant build file here and we need to add couple of target to it to be able to work with Selenium grid. I have taken these extra target from the Selenium Grid distribution, these are -












Target - "launch-hub" is used to launch grid hub while target "launch-remote-control" is used to launch remote controls along with set of parameters like - host, hubURL etc, which would be serving to hub.

Also notice that from previous post on ant build I have "pathelement" defined in "setclasspath" target.
This is to make sure that while starting the hub "grid_configuration.yml" is picked up from your project root folder and not the one available in selenium-grid jar files -






And now to start the Selenium RC server - the hub. Go to your project root folder on console and execute task - "ant launch-hub" and hub is launched with the configuration you specify in "grid_configuration.yml" file -

and Now is the turn of launching RC servers with configurations defined in "grid_configuration.yml" file. We would launch two RC servers one - "Firefox on Window" and "IE on Windows" on ports 5555 and 6666 respectively -

  and another RC server -



And now you have to specify configuration of browser environment in you testng.xml file along with the hub port - 4444


And now to run your selenium tests you need to execute target "run" from another console. You would see two browsers launched locally running your tests one on IE and other on Firefox

Comments

  1. Complex Post. This record helped me in my college assignment. Thnaks Alot

    ReplyDelete
  2. Hi Tarun,here is d abnormalitiy.
    1>The window is not getting maximized
    2>using selenium.focus is not working properly,focusiing other open window and working on that,so test cases getting failed.but after clearing cache it is working fine again.
    3>Also egarding command prompt window,i am sending u the mail as here is no scope for attachment.pls help.hpw to close them automatically or open only one commane window?

    ReplyDelete
  3. Hi Tarun,here is d abnormalitiy.
    1>The window is not getting maximized
    2>using selenium.focus is not working properly,focusiing other open window and working on that,so test cases getting failed.but after clearing cache it is working fine again.
    3>Also egarding command prompt window,i am sending u the mail as here is no scope for attachment.pls help.hpw to close them automatically or open only one commane window?

    ReplyDelete

Post a Comment

No spam only genuine comments :)

Popular posts from this blog

Distributed Load Testing with JMeter

Distributed Testing with JMeter When one JMeter client is not able to offer amount of threads required for load testing then distributed testing is used. In distributed testing - One instance of JMeter client can control number of JMeter instances and collect data from them Test plan does not need to be copied to each server, the client sends it to all servers note - JMeter will run all the threads on all the servers, hence 100 threads on 5 JMeter server would pump 500 threads in total. If many server instances are used, the client JMeter can become overloaded and so the client network connection. This has been improved in latest versions of JMeter by switching to Stripped modes, but you should always check that your client is not overloaded When Client (master) and Server (slave) nodes are on same network (no SSH required) Configure Client Node Herein client is referred as the machine controlling test execution on other JMeter nodes. This is also referred

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro

XPath and single quotes

I had tough time dealing with XPath and single quote. Though W3C recommends using ' to escape it but I never got it working, let me know if any of you get through. Came across this blog and found that “concat” could be used in this situation. So original XPath expression is – //meta[@name=’DESCRIPTION’][@content=’Tester’s Test’] This is some thing which certainly fails as single quote in “Tester’s” marks it at end of string and then XPath blows up, next trial was – //meta[@name=’DESCRIPTION’][@content=’Tester''s Test’] This does not work despite w3c recommendation! And then I used concat function and split the string as – concat(‘Tester’,”’”,’s Test’) NOTICE that single quote is kept in double quote while other characters are kept in single quotes. So XPath looks as – //meta[@name=’DESCRIPTION’][@content=concat(‘Tester’,”’”,’s Test’)] And this works charm.