{"id":15,"date":"2008-05-07T18:02:57","date_gmt":"2008-05-07T12:32:57","guid":{"rendered":"https:\/\/2thenew.xyz\/blog\/?p=15"},"modified":"2015-07-10T13:14:32","modified_gmt":"2015-07-10T07:44:32","slug":"web-testing-using-selenium-fix-for-error-javalangnullpointerexception-sessionid-should-not-be-null-has-this-session-been-started-yet","status":"publish","type":"post","link":"https:\/\/2thenew.xyz\/blog\/web-testing-using-selenium-fix-for-error-javalangnullpointerexception-sessionid-should-not-be-null-has-this-session-been-started-yet\/","title":{"rendered":"Web Testing using Selenium – fix for error “java.lang.NullPointerException: sessionId should not be null; has this session been started yet?”"},"content":{"rendered":"

I have a big fan of Selenium and have been using Selenium for quite some time for testing of web-applications.<\/p>\n

Recently, I upgraded my machine to Ubuntu Hardy Heron<\/a> and the next day, I found that all the selenium tests started failling on my machine. On digging through the logs, I found the following information in the Selenium Server logs:<\/p>\n

java.lang.RuntimeException: File was a script file, not a real executable: \/usr\/bin\/firefox-bin<\/code><\/p>\n

Before actually spotting this line, I was mis-led by other log messages; but I will not talk about them in this post.<\/p>\n

The reason for the failing tests was that Selenium Server thought that the default executable found in the path (\/usr\/bin\/firefox) was a script file and not an executable application for the browser. I am not sure why Selenium Server checks whether the path to the browser should not be a script.<\/p>\n

The cause of the problem is that because of\u00a0 Ubuntu Hardy Heron upgrade, my firefox also got upgraded from 2.x to 3.x. The firefox browser executable in 2.x is a binary file; whereas for firefox 3.x, it is a script (.sh) file. As a result of this change, the check done by\u00a0 Selenium Server was failing.<\/p>\n

I resolved this problem by providing explicit path to the Firefox 2 executable file in the java code. (I also tried providing explicit path to the Firefox 3 executable but that is no help).<\/p>\n

So, the code for the Java Selenium test-case looks like this :<\/p>\n

selenium = new DefaultSelenium(\"localhost\", 4444, \"*firefox \/usr\/lib\/firefox\/firefox-2-bin\", url);<\/code><\/p>\n

This is not a solution, if you want to test your app with Firefox 3. I haven’t figured out the solution for making it work with Firefox 3; but for the time being, I am happy with testing my application with Firefox 2.<\/p>\n

If somebody has a solution for making it work with Firefox 3, please post the solution as a comment to the blog.<\/p>\n

-Deepak<\/p>\n","protected":false},"excerpt":{"rendered":"

I have a big fan of Selenium and have been using Selenium for quite some time for testing of web-applications. Recently, I upgraded my machine to Ubuntu Hardy Heron and the next day, I found that all the selenium tests started failling on my machine. On digging through the logs, I found the following information […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":7,"footnotes":""},"categories":[1],"tags":[26,25,8],"class_list":["post-15","post","type-post","status-publish","format-standard","hentry","category-technology","tag-firefox","tag-selenium","tag-ubuntu"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t