Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When "app_location" is removed from config.yaml, test fails, "Null Pointer Exception" is generated. #65

Closed
mfaisalkhatri opened this issue Oct 1, 2018 · 0 comments
Assignees
Labels
type: bug Issue raised as a Bug.
Milestone

Comments

@mfaisalkhatri
Copy link
Collaborator

Description

When "app_location" is removed from the config.yaml file, null pointer exception is generated. Also, the error is not captured in coteafs-error log file.

Environment

  • Appium server version: 1.9.0
  • Desktop OS version: Windows 10
  • coteafs-appium version: develop-3.0.0
  • Mobile platform version: android/8.1.0
  • Real device / simulator: Real

Details

Following is the Stack trace of the code:
[RemoteTestNG] detected TestNG version 6.14.3
FAILED CONFIGURATION: @BeforeSuite setupSuite
java.lang.NullPointerException
at com.github.wasiqb.coteafs.appium.config.DeviceSetting.getAppLocation(DeviceSetting.java:84)
at com.github.wasiqb.coteafs.appium.device.Device.setAndroidCapabilities(Device.java:276)
at com.github.wasiqb.coteafs.appium.device.Device.setDeviceSpecificCapabilities(Device.java:320)
at com.github.wasiqb.coteafs.appium.device.Device.buildCapabilities(Device.java:199)
at com.github.wasiqb.coteafs.appium.device.Device.(Device.java:133)
at com.github.wasiqb.coteafs.appium.android.AndroidDevice.(AndroidDevice.java:37)
at com.flipkart.FlipkartAppTest.FlipkartBasicTest.setupSuite(FlipkartBasicTest.java:20)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:124)
at org.testng.internal.MethodInvocationHelper.invokeMethodConsideringTimeout(MethodInvocationHelper.java:59)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:458)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:222)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:142)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:401)
at org.testng.SuiteRunner.run(SuiteRunner.java:364)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:84)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1208)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1137)
at org.testng.TestNG.runSuites(TestNG.java:1049)
at org.testng.TestNG.run(TestNG.java:1017)
at org.testng.remote.AbstractRemoteTestNG.run(AbstractRemoteTestNG.java:114)
at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:251)
at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:77)

@mfaisalkhatri mfaisalkhatri added the type: bug Issue raised as a Bug. label Oct 1, 2018
@WasiqB WasiqB self-assigned this Oct 2, 2018
@WasiqB WasiqB added this to the Version 3.0.0 milestone Oct 2, 2018
WasiqB added a commit that referenced this issue Oct 2, 2018
@WasiqB WasiqB closed this as completed Oct 2, 2018
@WasiqB WasiqB mentioned this issue Nov 16, 2018
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Issue raised as a Bug.
Projects
None yet
Development

No branches or pull requests

2 participants