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.

Sign up for GitHub

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

Jump to bottom

Add unit tests for running the test within the mobile browser. #168

Open
mfaisalkhatri opened this issue Jul 8, 2021 · 3 comments
Open

Add unit tests for running the test within the mobile browser. #168

mfaisalkhatri opened this issue Jul 8, 2021 · 3 comments
Assignees
@WasiqB
Labels
effort: 1 1 story point no-issue-activity Issue having no activity for long time. platform: android Issue related to Android platform platform: ios Issue related to iOS platform priority: p1 Priority 1 issue. severity: high Issue is marked as high. state: pending Issue is in pending state awaiting to be worked on. type: docs Documentation needs to be updated. type: testing Issue is being tested. work: obvious Issue involving simple obvious work.
Milestone
Version-5.0.0

Comments

@mfaisalkhatri
Copy link
Collaborator

As per the query raised in #167 @WasiqB we need to add tests for mobile browsers as well for both iOS as well as android.
Also, a sample config file with mobile browser setting needs to be updated in the documentation as well.
@mfaisalkhatri mfaisalkhatri added type: docs Documentation needs to be updated. work: obvious Issue involving simple obvious work. labels Jul 8, 2021
@WasiqB WasiqB added effort: 1 1 story point platform: android Issue related to Android platform platform: ios Issue related to iOS platform priority: p1 Priority 1 issue. severity: high Issue is marked as high. state: pending Issue is in pending state awaiting to be worked on. type: testing Issue is being tested. labels Jul 18, 2021
@WasiqB WasiqB added this to the Version-4.1.0 milestone Jul 18, 2021
@WasiqB WasiqB mentioned this issue Jul 24, 2021
Closed
@WasiqB WasiqB linked a pull request Jul 25, 2021 that will close this issue
Release v-4.1.0 #172
Merged
5 tasks
@mfaisalkhatri
Copy link
Collaborator Author

Following stack trace is generated while trying to run the tests on browser

java.lang.NullPointerException: Cannot invoke "com.github.wasiqb.coteafs.appium.config.device.android.WebOptions.getArgs()" because "options" is null

	at com.github.wasiqb.coteafs.appium.device.Device.setChromeOptions(Device.java:393)
	at com.github.wasiqb.coteafs.appium.device.Device.setAndroidWebSetting(Device.java:380)
	at com.github.wasiqb.coteafs.appium.device.Device.setAndroidCapabilities(Device.java:370)
	at com.github.wasiqb.coteafs.appium.device.Device.setDeviceSpecificCapabilities(Device.java:430)
	at com.github.wasiqb.coteafs.appium.device.Device.setLocalCapabilities(Device.java:492)
	at com.github.wasiqb.coteafs.appium.device.Device.buildCapabilities(Device.java:288)
	at com.github.wasiqb.coteafs.appium.device.Device.<init>(Device.java:153)
	at com.github.wasiqb.coteafs.appium.android.AndroidDevice.<init>(AndroidDevice.java:40)
	at tests.DefaultTest.setupTest(DefaultTest.java:26)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:564)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:133)
	at org.testng.internal.MethodInvocationHelper.invokeMethodConsideringTimeout(MethodInvocationHelper.java:62)
	at org.testng.internal.ConfigInvoker.invokeConfigurationMethod(ConfigInvoker.java:385)
	at org.testng.internal.ConfigInvoker.invokeConfigurations(ConfigInvoker.java:321)
	at org.testng.TestRunner.invokeTestConfigurations(TestRunner.java:637)
	at org.testng.TestRunner.beforeRun(TestRunner.java:627)
	at org.testng.TestRunner.run(TestRunner.java:589)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:377)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:371)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:332)
	at org.testng.SuiteRunner.run(SuiteRunner.java:276)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1212)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1134)
	at org.testng.TestNG.runSuites(TestNG.java:1063)
	at org.testng.TestNG.run(TestNG.java:1031)
	at com.intellij.rt.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:66)
	at com.intellij.rt.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:109)

@WasiqB WasiqB modified the milestones: Version-4.1.0, Version-5.0.0 Aug 7, 2021
@WasiqB WasiqB removed a link to a pull request Aug 7, 2021
Release v-4.1.0 #172
Merged
5 tasks
@github-actions
Copy link

github-actions bot commented Nov 6, 2021

Ticket is stale since last 90 days.

@github-actions github-actions bot added the no-issue-activity Issue having no activity for long time. label Nov 6, 2021
@WasiqB WasiqB removed the no-issue-activity Issue having no activity for long time. label Jan 11, 2022
@github-actions
Copy link

Ticket is stale since last 90 days.

@github-actions github-actions bot added the no-issue-activity Issue having no activity for long time. label Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@WasiqB WasiqB

Labels
effort: 1 1 story point no-issue-activity Issue having no activity for long time. platform: android Issue related to Android platform platform: ios Issue related to iOS platform priority: p1 Priority 1 issue. severity: high Issue is marked as high. state: pending Issue is in pending state awaiting to be worked on. type: docs Documentation needs to be updated. type: testing Issue is being tested. work: obvious Issue involving simple obvious work.
Projects
None yet
Milestone
Version-5.0.0
Development

No branches or pull requests
2 participants
@WasiqB @mfaisalkhatri