java.lang.NullPointerException: This exception has no message.


Samebug tips

Take a look at this blog post on how to set up Grid2 https://goo.gl/rxzbE6. A user related (in the email group on the source) that using older selenium libs solves this exception.


5 months ago
Expert tip

Solutions on the web

Solution icon of googlegroups
This exception has no message.

Solution icon of github
via GitHub by MJRLegends
, 7 months ago
This exception has no message.

Solution icon of github
via GitHub by Minjung-Baek
, 1 year ago
This exception has no message.

Solution icon of github
via GitHub by amsolano426
, 8 months ago
This exception has no message.

Solution icon of github
via GitHub by Proplex
, 1 year ago
This exception has no message.

Solution icon of github
via GitHub by Ironic8b498
, 1 year ago
This exception has no message.

Solution icon of github
via GitHub by stucki
, 9 months ago
This exception has no message.

Solution icon of github
via GitHub by stucki
, 11 months ago
This exception has no message.

Solution icon of github
via GitHub by lberki
, 1 year ago
This exception has no message.

Solution icon of github
via GitHub by jarlfr
, 1 year ago
This exception has no message.

Stack trace

java.lang.NullPointerException
	at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:770)
	at org.openqa.selenium.interactions.Actions.<init>(Actions.java:71)
	at automationFramework.LoginTest.TestFireFox(LoginTest.java:50)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:108)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:661)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:869)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1193)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:126)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
	at org.testng.TestRunner.privateRun(TestRunner.java:744)
	at org.testng.TestRunner.run(TestRunner.java:602)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:380)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:375)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:340)
	at org.testng.SuiteRunner.run(SuiteRunner.java:289)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1301)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1226)
	at org.testng.TestNG.runSuites(TestNG.java:1144)
	at org.testng.TestNG.run(TestNG.java:1115)
	at org.testng.remote.AbstractRemoteTestNG.run(AbstractRemoteTestNG.java:132)
	at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:230)
	at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:76)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Once, 1 day ago
3 times, 3 months ago
119 times, 1 month ago
Once, 5 months ago
3 times, 5 months ago
88 more bugmates