Getting timeout on my OnePlus 5T while running Appium - java

I am using Appium version 1.15.0 and while running my Appium app automation suite on my OnePlus 5T, I am getting error : An unknown server-side error occurred while processing the command. Original error: Failed to launch Appium Settings app: Condition unmet after 5441 ms. Timing out.

Related

Firefox Driver fails with org.openqa.selenium.SessionNotCreatedException:

I am getting this exception when running tests in Firefox.
com.codeborne.selenide.ex.SoftAssertionError: Test DraftTest.setUp failed (3 failures)
org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
at com.codeborne.selenide.logevents.ErrorsCollector.cleanAndGetAssertionError(ErrorsCollector.java:64)
at com.codeborne.selenide.testng.SoftAsserts.failIfErrors(SoftAsserts.java:91)
at com.codeborne.selenide.testng.SoftAsserts.onConfigurationFailure(SoftAsserts.java:46)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
com.intellij.rt.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:66)
at com.intellij.rt.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:109)
Firefox version: 98.0.1
Selenide version: 6.3.4 (Selenium 4.1.2)
I was getting the same error running my tests using Selenium 4.3.0 and Firefox 91.6. I downloaded the latest geckodriver from here (0.31.0 at the time of this writing) and that resolved the issue for me.

Android Studio Emulator wont start

So everything was working fine, today I opened android studio and try to run the emulator, and it wont start. I will provide the errors in an image bellow.
I tried wiping the emulators data , and disabled the antivirus, I tried new device...
Please help I need it :(
ERRORS OF EMULATOR PICTURE
11:45 AM Gradle sync started
11:45 AM Gradle sync finished in 2 s 250 ms (from cached state)
11:46 AM Executing tasks: [clean, :app:assembleDebug] in project D:\AndroidStudioProjects\AudioVideo
11:47 AM Gradle build finished in 47 s 998 ms
11:47 AM Executing tasks: [:app:assembleDebug] in project D:\AndroidStudioProjects\AudioVideo
11:47 AM Gradle build finished in 20 s 141 ms
11:48 AM Emulator: emulator: WARNING: EmulatorService.cpp:448: Cannot find certfile: C:\Users\User.android\emulator-grpc.cer security will be disabled.
11:48 AM Emulator: Started GRPC server at 127.0.0.1:8554
11:48 AM Emulator: C:\Users\User\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: error while loading state for instance 0x0 of device 'goldfish_pipe'
11:48 AM Emulator: deleteSnapshot: for default_boot
11:48 AM Emulator: Process finished with exit code 0
11:49 AM Executing tasks: [:app:assembleDebug] in project D:\AndroidStudioProjects\AudioVideo
11:49 AM Gradle build finished in 5 s 906 ms
Possible solutions
Invalidate/Restart Android studio
Open AVD Manager select you emulator and wipe Data from the dropdown
Installing Intel latest Intel HAXM
or delete current emulator and install new one
I want to say, that any possible solution did not work for me, I lost 4 hours working on that. I quit and installed Genymotion , I can tell that it runned smoother than the android emulator.

java.lang.RuntimeException: org.openqa.selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally

I trying to render the webpage using chromedriver on centos7.I have installed both google-chrome and chromedriver .I am starting the chromedriver using the following command.
$ chromedriver --port=9515 --headless --whitelisted-ips="myip" --disable-dev-shm-usage --log-path='chrome.log'
Starting ChromeDriver 74.0.3729.6 (255758eccf3d244491b8a1317aa76e1ce10d57e9-refs/branch-heads/3729#{#29}) on port 9515
Remote connections are allowed by a whitelist (myip).
Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.
I am running the google chrome using the following command
$ google-chrome --headless --remote-debugging-port=9222 --disable-gpu
xcb_connection_has_error() returned true
DevTools listening on ws://127.0.0.1:9222/devtools/browser/cf6b15dd-0e37-4106-88ed-01b959252da4
Here we have google-chrome and chromedriver running.But when my Java application try to connect to the port at which the chromedriver is running i am getting the following error
java.lang.RuntimeException: org.openqa.selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
(Driver info: chromedriver=74.0.3729.6 (255758eccf3d244491b8a1317aa76e1ce10d57e9-refs/branch-heads/3729#{#29}),platform=Linux 3.10.0-862.3.2.el7.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)
I have tried out the same in my windows environment it works fine.
version:
ChromeDriver 74.0.3729.6
Google Chrome 74.0.3729.131

Getting error for selenium test execution with jenkins on QAT server, it's working fine with local jenkins

Currently, I am doing automation of a project and writing Tests thru selenium and java it's working fine when I am executing tests from
Jenkins on my local server but on QAT I am getting an error.Previously I have written selenium test and now I have started using Jenkins for build and integration with Git on my windows platform.
Also, chrome path I am using for QAT server is I have changed to
System.setProperty("webdriver.chrome.driver", "C:\Program Files
(x86)\Jenkins\jobs\SPOSAUTOMATION\workspace\Driver\chromedriver.exe");
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
Starting ChromeDriver 2.32.498550
(9dec58e66c31bcc53a9ce3c7226f0c1c5810906a) on port 10309
Only local connections are allowed.
[ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time
elapsed: 21.404 s <<< FAILURE! - in TestSuite
[ERROR]
launchBrowserTest(com.Spos.LoginAppUserAdmin.LoginAppUserAdmin) Time
elapsed: 21.248 s <<< FAILURE!
org.openqa.selenium.WebDriverException:
Timed out waiting for driver server to start.
This is the log file generated after execution build test thru Jenkins on
QAT server of the application.Here chromedriver started execution but not getting connected with chrome server and throwing a timeout exception.
Please ask me if any further information required to resolve the issue.
Is your selenium server active on the machine you are trying to execute the code through Jenkins?
you can check that, and start the server on command line from the location where selenium standalone server is located. Try the following command(modify the paths) :
java -jar selenium-server-standalone-2.53.1.jar -Dwebdriver.chrome.driver=c:\path\to\chromedriver.exe
Which OS you are using on your http://192.168.10.91:8081/ (server)? If it is Ubuntu then try executing scripts in headless mode and follow these steps:
Download and enable Xvfb before the start of selenium script on Jenkins. For more info read here https://wiki.jenkins.io/display/JENKINS/Xvfb+Plugin
To be on safer side try to keep chromedriver in "usr/bin" folder.
Now run the script.

Android ADB detect emulator as offline

When I run my codes, the android ADB detect the emulator as offline, although I have turned on the emulator. I am using AMD processor. I'm running armebiv7 device image.
Here's the error that I get.
emulator: WARNING: Crash service did not start
emulator: WARNING: Classic qemu does not support SMP. The hw.cpu.ncore > option from your config file is ignored.
emulator: Listening for console connections on port: 5554
emulator: Serial number of this emulator (for ADB): emulator-5554
emulator: WARNING: UpdateCheck: Failure: Error
Thanks!

Categories

Resources