Hello everyone I need your help.
I want to run appium via the command line, but I get constant errors. I suffered for a long time and decided to seek help.
The emulator is installed, the correct apk path, updated all appium versions.
D:\VSC\Webdriverio-appium>npx wdio
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
Execution of 1 workers started at 2023-02-13T13:31:11.269Z
2023-02-13T13:31:11.499Z INFO #wdio/cli:launcher: Run onPrepare hook
2023-02-13T13:31:36.561Z INFO #wdio/cli:launcher: Run onWorkerStart hook
2023-02-13T13:31:36.570Z INFO #wdio/local-runner: Start worker 0-0 with arg:
[0-0] 2023-02-13T13:31:42.271Z INFO #wdio/local-runner: Run worker command: run
[0-0] RUNNING in Android - file:///D:/VSC/Webdriverio-appium/test/specs/example.e2e.js
[0-0] 2023-02-13T13:31:43.192Z INFO webdriver: Initiate new session using the WebDriver protocol
[0-0] 2023-02-13T13:31:43.772Z INFO webdriver: [POST] http://127.0.0.1:4723/session
[0-0] 2023-02-13T13:31:43.773Z INFO webdriver: DATA {
[0-0] capabilities: {
[0-0] alwaysMatch: {
[0-0] platformName: 'Android',
[0-0] 'appium:platformVersion': '11.0',
[0-0] 'appium:automationName': 'UIAutomator2',
[0-0] 'appium:deviceName': 'Pixel 3',
[0-0] 'appium:app': 'D:\\VSC\\Webdriverio-appium\\D:VSCWebdriverio-appiumappAndroidapp.apk'
[0-0] },
[0-0] firstMatch: [ {} ]
[0-0] },
[0-0] desiredCapabilities: {
[0-0] platformName: 'Android',
[0-0] 'appium:platformVersion': '11.0',
[0-0] 'appium:automationName': 'UIAutomator2',
[0-0] 'appium:deviceName': 'Pixel 3',
[0-0] 'appium:app': 'D:\\VSC\\Webdriverio-appium\\D:VSCWebdriverio-appiumappAndroidapp.apk'
[0-0] }
[0-0] }
[0-0] 2023-02-13T13:31:44.254Z WARN webdriver: Request failed with status 500 due to An unknown server-side error occurred while processing the command. Original error: The application at 'D:\VSC\Webdriverio-appium\D:VSCWebdriverio-appiumappAndroidapp.apk' does not exist or is not accessible
[0-0] 2023-02-13T13:31:44.255Z INFO webdriver: Retrying 1/3
[0-0] 2023-02-13T13:31:44.257Z INFO webdriver: [POST] http://127.0.0.1:4723/session
[0-0] 2023-02-13T13:31:44.257Z INFO webdriver: DATA {
[0-0] capabilities: {
[0-0] alwaysMatch: {
[0-0] platformName: 'Android',
[0-0] 'appium:platformVersion': '11.0',
[0-0] 'appium:automationName': 'UIAutomator2',
[0-0] 'appium:deviceName': 'Pixel 3',
[0-0] 'appium:app': 'D:\\VSC\\Webdriverio-appium\\D:VSCWebdriverio-appiumappAndroidapp.apk'
[0-0] },
[0-0] firstMatch: [ {} ]
[0-0] },
[0-0] desiredCapabilities: {
[0-0] platformName: 'Android',
[0-0] 'appium:platformVersion': '11.0',
[0-0] 'appium:automationName': 'UIAutomator2',
[0-0] 'appium:deviceName': 'Pixel 3',
[0-0] 'appium:app': 'D:\\VSC\\Webdriverio-appium\\D:VSCWebdriverio-appiumappAndroidapp.apk'
[0-0] }
[0-0] }
[0-0] 2023-02-13T13:31:44.344Z WARN webdriver: Request failed with status 500 due to An unknown server-side error occurred while processing the command. Original error: The application at 'D:\VSC\Webdriverio-appium\D:VSCWebdriverio-appiumappAndroidapp.apk' does not exist or is not accessible
[0-0] 2023-02-13T13:31:44.345Z INFO webdriver: Retrying 2/3
[0-0] 2023-02-13T13:31:44.345Z INFO webdriver: [POST] http://127.0.0.1:4723/session
[0-0] 2023-02-13T13:31:44.346Z INFO webdriver: DATA {
[0-0] capabilities: {
[0-0] alwaysMatch: {
[0-0] platformName: 'Android',
[0-0] 'appium:platformVersion': '11.0',
[0-0] 'appium:automationName': 'UIAutomator2',
[0-0] 'appium:deviceName': 'Pixel 3',
[0-0] 'appium:app': 'D:\\VSC\\Webdriverio-appium\\D:VSCWebdriverio-appiumappAndroidapp.apk'
[0-0] },
[0-0] firstMatch: [ {} ]
[0-0] },
[0-0] desiredCapabilities: {
[0-0] platformName: 'Android',
[0-0] 'appium:platformVersion': '11.0',
[0-0] 'appium:automationName': 'UIAutomator2',
[0-0] 'appium:deviceName': 'Pixel 3',
[0-0] 'appium:app': 'D:\\VSC\\Webdriverio-appium\\D:VSCWebdriverio-appiumappAndroidapp.apk'
[0-0] }
[0-0] }
[0-0] 2023-02-13T13:31:44.448Z WARN webdriver: Request failed with status 500 due to An unknown server-side error occurred while processing the command. Original error: The application at 'D:\VSC\Webdriverio-appium\D:VSCWebdriverio-appiumappAndroidapp.apk' does not exist or is not accessible
[0-0] 2023-02-13T13:31:44.448Z INFO webdriver: Retrying 3/3
[0-0] 2023-02-13T13:31:44.449Z INFO webdriver: [POST] http://127.0.0.1:4723/session
[0-0] 2023-02-13T13:31:44.449Z INFO webdriver: DATA {
[0-0] capabilities: {
[0-0] alwaysMatch: {
[0-0] platformName: 'Android',
[0-0] 'appium:platformVersion': '11.0',
[0-0] 'appium:automationName': 'UIAutomator2',
[0-0] 'appium:deviceName': 'Pixel 3',
[0-0] 'appium:app': 'D:\\VSC\\Webdriverio-appium\\D:VSCWebdriverio-appiumappAndroidapp.apk'
[0-0] },
[0-0] firstMatch: [ {} ]
[0-0] },
[0-0] desiredCapabilities: {
[0-0] platformName: 'Android',
[0-0] 'appium:platformVersion': '11.0',
[0-0] 'appium:automationName': 'UIAutomator2',
[0-0] 'appium:deviceName': 'Pixel 3',
[0-0] 'appium:app': 'D:\\VSC\\Webdriverio-appium\\D:VSCWebdriverio-appiumappAndroidapp.apk'
[0-0] }
[0-0] }
[0-0] 2023-02-13T13:31:44.581Z ERROR webdriver: Request failed with status 500 due to unknown error: An unknown server-side error occurred while processing the command. Original error: The application at 'D:\VSC\Webdriverio-appium\D:VSCWebdriverio-appiumappAndroidapp.apk' does not exist or is not accessible
[0-0] 2023-02-13T13:31:44.582Z ERROR webdriver: unknown error: An unknown server-side error occurred while processing the command. Original error: The application at 'D:\VSC\Webdriverio-appium\D:VSCWebdriverio-appiumappAndroidapp.apk' does not exist or is not accessible
[0-0] at getErrorFromResponseBody (file:///D:/VSC/Webdriverio-appium/node_modules/webdriver/build/utils.js:194:12)
[0-0] at NodeJSRequest._request (file:///D:/VSC/Webdriverio-appium/node_modules/webdriver/build/request/index.js:164:23)
[0-0] at processTicksAndRejections (node:internal/process/task_queues:96:5)
[0-0] at startWebDriverSession (file:///D:/VSC/Webdriverio-appium/node_modules/webdriver/build/utils.js:63:20)
[0-0] at Function.newSession (file:///D:/VSC/Webdriverio-appium/node_modules/webdriver/build/index.js:24:45)
[0-0] at remote (file:///D:/VSC/Webdriverio-appium/node_modules/webdriverio/build/index.js:48:22)
[0-0] at Runner._startSession (file:///D:/VSC/Webdriverio-appium/node_modules/#wdio/runner/build/index.js:221:29)
[0-0] at Runner._initSession (file:///D:/VSC/Webdriverio-appium/node_modules/#wdio/runner/build/index.js:187:25)
[0-0] at Runner.run (file:///D:/VSC/Webdriverio-appium/node_modules/#wdio/runner/build/index.js:77:19)
[0-0] 2023-02-13T13:31:44.587Z ERROR #wdio/runner: Error: Failed to create session.
[0-0] An unknown server-side error occurred while processing the command. Original error: The application at 'D:\VSC\Webdriverio-appium\D:VSCWebdriverio-appiumappAndroidapp.apk' does not exist or is not accessible
[0-0] at startWebDriverSession (file:///D:/VSC/Webdriverio-appium/node_modules/webdriver/build/utils.js:68:15)
[0-0] at processTicksAndRejections (node:internal/process/task_queues:96:5)
[0-0] at Function.newSession (file:///D:/VSC/Webdriverio-appium/node_modules/webdriver/build/index.js:24:45)
[0-0] at remote (file:///D:/VSC/Webdriverio-appium/node_modules/webdriverio/build/index.js:48:22)
[0-0] at Runner._startSession (file:///D:/VSC/Webdriverio-appium/node_modules/#wdio/runner/build/index.js:221:29)
[0-0] at Runner._initSession (file:///D:/VSC/Webdriverio-appium/node_modules/#wdio/runner/build/index.js:187:25)
[0-0] at Runner.run (file:///D:/VSC/Webdriverio-appium/node_modules/#wdio/runner/build/index.js:77:19)
[0-0] FAILED in Android - file:///D:/VSC/Webdriverio-appium/test/specs/example.e2e.js
2023-02-13T13:31:44.800Z INFO #wdio/cli:launcher: Run onWorkerEnd hook
2023-02-13T13:31:44.813Z INFO #wdio/cli:launcher: Run onComplete hook
Spec Files: 0 passed, 1 failed, 1 total (100% completed) in 00:00:33
2023-02-13T13:31:44.826Z INFO #wdio/local-runner: Shutting down spawned worker
2023-02-13T13:31:45.112Z INFO #wdio/local-runner: Waiting for 0 to shut down gracefully
2023-02-13T13:31:45.116Z INFO #wdio/local-runner: shutting down
What to pay attention to. It seems to me that I've double-checked everything. And I don't quite understand what I missed. Thanks
Related
I am new to webdriver io. I ran my cucumber test and it fails with this error
`[0-0] 2023-02-14T21:47:36.064Z WARN webdriver: Request failed with status 400 due to invalid argument: unrecognized capability: pollTimeout
[0-0] 2023-02-14T21:47:36.065Z INFO webdriver: Retrying 1/3
[0-0] 2023-02-14T21:47:36.066Z INFO webdriver: [POST] http://localhost:9515/session
[0-0] 2023-02-14T21:47:36.066Z INFO webdriver: DATA {
[0-0] capabilities: {
[0-0] alwaysMatch: {
[0-0] browserName: 'chrome',
[0-0] acceptInsecureCerts: true,
[0-0] pollTimeout: 10000
[0-0] },
[0-0] firstMatch: [ {} ]
[0-0] },
[0-0] desiredCapabilities: {
[0-0] browserName: 'chrome',
[0-0] acceptInsecureCerts: true,
[0-0] pollTimeout: 10000
[0-0] }
[0-0] }`
Any suggesion on how i can resolve this please?
i tried to comment out waitforTimeout: 10000, in wdio.config.js but it doesnt solve the problem
I solved the problem for myself. I uninstall node and install them with brew to the next version (19.6.0).
After that - 500. Because, chromedriver don`t support Chrome. After that, I updated Google chrome and everything worked.
I install new node version and re-init the wdio, now it work.
WebdriverIO Use
wdio.conf.js
maxInstances: 1,
capabilities: [{
platformName: 'iOS',
noReset: true,
fullReset: false,
maxInstances: 1,
automationName: 'XCUITest',
deviceName: 'iPhone 11',
platformVersion: '14.5',
app: path.resolve(`. /{app}.zip`),
}],
waitforTimeout: 10000,
connectionRetryTimeout: 50000,
connectionRetryCount: 6,
services: [
'appium'.
],
appium: {
command: 'appium',
args: {},
},
port: 4723,
path: '/wd/hub',
azure-pipelines.yml
- script: |
npm install -g appium
appium &.
sudo xcode-select -s /Applications/Xcode_12.5.app/Contents/Developer
xcrun simctl list
After running the test, it takes about 10 minutes before the test actually starts.
Why is this?
Has anyone tried working with electron and webdriverio? I am using the latest electron 16 version with "wdio-chromedriver-service": "^7.2.2" and chromedriver "96.0.0" version. I am getting the following error:
$ npx wdio run ./wdio.conf.js --spec welcome-test.e2e.js
Execution of 1 workers started at 2021-11-30T11:14:38.431Z
2021-11-30T11:14:38.516Z INFO #wdio/cli:launcher: Run onPrepare hook
2021-11-30T11:14:38.517Z INFO chromedriver: Start Chromedriver (C:\Projects\abc\node_modules\chromedriver\lib\chromedriver\chromedriver.exe) with args --silent --port=9515 --url-base=/
2021-11-30T11:14:38.652Z INFO #wdio/cli:launcher: Run onWorkerStart hook
2021-11-30T11:14:38.657Z INFO #wdio/local-runner: Start worker 0-0 with arg: run,./wdio.conf.js,--spec,welcome-test.e2e.js
[0-0] 2021-11-30T11:14:39.340Z INFO #wdio/local-runner: Run worker command: run
[0-0] RUNNING in chrome - C:\Projects\abc\test\specs\welcome-test.e2e.js
[0-0] 2021-11-30T11:14:40.069Z INFO webdriver: Initiate new session using the WebDriver protocol
[0-0] 2021-11-30T11:14:40.136Z INFO webdriver: [POST] http://localhost:9515/session
[0-0] 2021-11-30T11:14:40.137Z INFO webdriver: DATA {
[0-0] capabilities: {
[0-0] alwaysMatch: {
[0-0] browserName: 'chrome',
[0-0] acceptInsecureCerts: true,
[0-0] 'goog:chromeOptions': [Object]
[0-0] },
[0-0] firstMatch: [ {} ]
[0-0] },
[0-0] desiredCapabilities: {
[0-0] browserName: 'chrome',
[0-0] acceptInsecureCerts: true,
[0-0] 'goog:chromeOptions': {
[0-0] binary: 'C:/Projects/abc/node_modules/electron/dist/electron.exe',
[0-0] args: [Array]
[0-0] }
[0-0] }
[0-0] }
[0-0] 2021-11-30T11:14:45.557Z WARN webdriver: Request failed with status 500 due to unknown error: Chrome failed to start: exited normally.
[0-0] (chrome not reachable)
[0-0] (The process started from chrome location C:/Projects/abc/node_modules/electron/dist/electron.exe is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
My wdio.conf.js file look like this:
capabilities: [{
// maxInstances can get overwritten per capability. So if you have an in-house Selenium
// grid with only 5 firefox instances available you can make sure that not more than
// 5 instances get started at a time.
maxInstances: 1,
browserName: 'chrome',
acceptInsecureCerts: true,
'goog:chromeOptions': {
binary: 'C:/Projects/abc/node_modules/electron/dist/electron.exe', // Path to your Electron binary.
args: ['app=C:/Projects/abc', '--no-sandbox', '--headless'], // Optional, perhaps 'app=' + /path/to/your/app/
},
// If outputDir is provided WebdriverIO can capture driver session logs
// it is possible to configure which logTypes to include/exclude.
// excludeDriverLogs: ['*'], // pass '*' to exclude all driver session logs
// excludeDriverLogs: ['bugreport', 'server'],
}],
Any help is appreciated.
I want to have three connected docker containers (to run it on a build server):
My application (name: app)
A browser (in this case chrome; name: selenium)
My End2End/UI-Tests (name tester)
However the tests aren't running. The current error message from the tester container is "Request failed with status 500 due to unknown error: net::ERR_SSL_PROTOCOL_ERROR"
file structure:
dir
test
specs
basic.js
app.js
docker-compose.yml
Dockerfile
package.json
wdio.conf.js
And here my files:
"docker-compose.yml":
version: '3'
services:
tester:
build:
context: .
target: e2e-tests
command: npx wdio wdio.conf.js
links:
- selenium
selenium:
image: selenium/standalone-chrome
expose:
- "4444"
links:
- app
app:
build:
context: .
target: prod
expose:
- "3000"
command: npm start
"Dockerfile":
FROM node:12 as base
WORKDIR /usr/src/app
COPY package*.json ./
RUN npm install
FROM base as prod
COPY app.js ./
EXPOSE 3000
FROM base as e2e-tests
COPY wdio.conf.js ./
COPY test test
"wdio.conf.js":
exports.config = {
hostname: 'selenium',
path: '/wd/hub',
specs: [
'./test/specs/**/*.js'
],
exclude: [],
maxInstances: 10,
capabilities: [{
maxInstances: 5,
browserName: 'chrome',
acceptInsecureCerts: true
}],
logLevel: 'info',
bail: 0,
baseUrl: 'http://localhost',
waitforTimeout: 10000,
connectionRetryTimeout: 120000,
connectionRetryCount: 3,
framework: 'jasmine',
reporters: ['spec'],
jasmineNodeOpts: {
defaultTimeoutInterval: 60000,
expectationResultHandler: function(passed, assertion) {}
},
}
"test/spec/basic.js":
describe('test app', () => {
it('should have the right title', () => {
browser.url('http://app:3000')
expect(browser).toHaveTextContaining('Hello');
})
})
"app.js":
const express = require('express');
const app = express();
app.get('/', (req, res) => res.send('<html><head><title>Hello</title></head><body>Hello World!</body></html>'));
const server = app.listen(3000, () => {
const { port } = server.address();
console.log(`Test app listening on port ${port}`);
});
"package.json":
{
"name": "wdiodocker",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"start": "node app.js"
},
"author": "",
"license": "ISC",
"dependencies": {
"express": "^4.17.1"
},
"devDependencies": {
"#wdio/cli": "^6.5.2",
"#wdio/jasmine-framework": "^6.5.0",
"#wdio/local-runner": "^6.5.2",
"#wdio/spec-reporter": "^6.4.7",
"#wdio/sync": "^6.5.0",
"wdio-docker-service": "^3.0.0"
}
}
"bigger snippet from the log":
tester_1 | 2020-09-28T07:55:11.844Z INFO #wdio/cli:launcher: Run onPrepare hook
tester_1 | 2020-09-28T07:55:11.848Z INFO #wdio/cli:launcher: Run onWorkerStart hook
tester_1 | 2020-09-28T07:55:11.850Z INFO #wdio/local-runner: Start worker 0-0 with arg: wdio.conf.js
selenium_1 | 07:55:12.017 INFO [GridLauncherV3.lambda$buildLaunchers$3] - Launching a standalone Selenium Server on port 4444
selenium_1 | 2020-09-28 07:55:12.150:INFO::main: Logging initialized #1038ms to org.seleniumhq.jetty9.util.log.StdErrLog
tester_1 | [0-0] 2020-09-28T07:55:12.634Z INFO #wdio/local-runner: Run worker command: run
tester_1 | [0-0] 2020-09-28T07:55:12.658Z INFO webdriverio: Initiate new session using the ./protocol-stub protocol
selenium_1 | 07:55:12.862 INFO [WebDriverServlet.<init>] - Initialising WebDriverServlet
tester_1 | [0-0] RUNNING in chrome - /test/specs/basic.js
tester_1 | [0-0] 2020-09-28T07:55:13.056Z INFO webdriverio: Initiate new session using the webdriver protocol
tester_1 | [0-0] 2020-09-28T07:55:13.060Z INFO webdriver: [POST] http://selenium:4444/wd/hub/session
tester_1 | [0-0] 2020-09-28T07:55:13.061Z INFO webdriver: DATA {
tester_1 | capabilities: {
tester_1 | alwaysMatch: { browserName: 'chrome', acceptInsecureCerts: true },
tester_1 | firstMatch: [ {} ]
tester_1 | },
tester_1 | desiredCapabilities: { browserName: 'chrome', acceptInsecureCerts: true }
tester_1 | }
selenium_1 | 07:55:13.122 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 4444
selenium_1 | 07:55:13.331 INFO [ActiveSessionFactory.apply] - Capabilities are: {
selenium_1 | "acceptInsecureCerts": true,
selenium_1 | "browserName": "chrome"
selenium_1 | }
selenium_1 | 07:55:13.335 INFO [ActiveSessionFactory.lambda$apply$11] - Matched factory org.openqa.selenium.grid.session.remote.ServicedSession$Factory (provider: org.openqa.selenium.chrome.ChromeDriverService)
selenium_1 | Starting ChromeDriver 85.0.4183.83 (94abc2237ae0c9a4cb5f035431c8adfb94324633-refs/branch-heads/4183#{#1658}) on port 24508
selenium_1 | Only local connections are allowed.
selenium_1 | Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
selenium_1 | ChromeDriver was started successfully.
selenium_1 | [1601279713.386][SEVERE]: bind() failed: Cannot assign requested address (99)
selenium_1 | 07:55:14.377 INFO [ProtocolHandshake.createSession] - Detected dialect: W3C
selenium_1 | 07:55:14.428 INFO [RemoteSession$Factory.lambda$performHandshake$0] - Started new session 82d59567606b7f101da8650600e7dd00 (org.openqa.selenium.chrome.ChromeDriverService)
tester_1 | [0-0] 2020-09-28T07:55:14.607Z INFO webdriver: COMMAND navigateTo("http://app:3000/")
tester_1 | [0-0] 2020-09-28T07:55:14.610Z INFO webdriver: [POST] http://selenium:4444/wd/hub/session/82d59567606b7f101da8650600e7dd00/url
tester_1 | [0-0] 2020-09-28T07:55:14.611Z INFO webdriver: DATA { url: 'http://app:3000/' }
tester_1 | [0-0] 2020-09-28T07:55:15.188Z WARN webdriver: Request failed with status 500 due to unknown error: net::ERR_SSL_PROTOCOL_ERROR
tester_1 | (Session info: chrome=85.0.4183.83)
tester_1 | [0-0] 2020-09-28T07:55:15.189Z INFO webdriver: Retrying 1/3
tester_1 | [0-0] 2020-09-28T07:55:15.190Z INFO webdriver: [POST] http://selenium:4444/wd/hub/session/82d59567606b7f101da8650600e7dd00/url
tester_1 | [0-0] 2020-09-28T07:55:15.191Z INFO webdriver: DATA { url: 'http://app:3000/' }
tester_1 | [0-0] 2020-09-28T07:55:15.592Z WARN webdriver: Request failed with status 500 due to unknown error: net::ERR_SSL_PROTOCOL_ERROR
tester_1 | (Session info: chrome=85.0.4183.83)
tester_1 | [0-0] 2020-09-28T07:55:15.592Z INFO webdriver: Retrying 2/3
tester_1 | [0-0] 2020-09-28T07:55:15.594Z INFO webdriver: [POST] http://selenium:4444/wd/hub/session/82d59567606b7f101da8650600e7dd00/url
tester_1 | [0-0] 2020-09-28T07:55:15.595Z INFO webdriver: DATA { url: 'http://app:3000/' }
tester_1 | [0-0] 2020-09-28T07:55:15.942Z WARN webdriver: Request failed with status 500 due to unknown error: net::ERR_SSL_PROTOCOL_ERROR
tester_1 | (Session info: chrome=85.0.4183.83)
tester_1 | [0-0] 2020-09-28T07:55:15.943Z INFO webdriver: Retrying 3/3
tester_1 | [0-0] 2020-09-28T07:55:15.944Z INFO webdriver: [POST] http://selenium:4444/wd/hub/session/82d59567606b7f101da8650600e7dd00/url
tester_1 | [0-0] 2020-09-28T07:55:15.945Z INFO webdriver: DATA { url: 'http://app:3000/' }
tester_1 | [0-0] 2020-09-28T07:55:16.104Z ERROR webdriver: Request failed with status 500 due to unknown error: unknown error: net::ERR_SSL_PROTOCOL_ERROR
tester_1 | (Session info: chrome=85.0.4183.83)
tester_1 | [0-0] Error in "test app should have the right title"
tester_1 | unknown error: unknown error: net::ERR_SSL_PROTOCOL_ERROR
tester_1 | (Session info: chrome=85.0.4183.83)
tester_1 | [0-0] 2020-09-28T07:55:16.118Z INFO webdriver: COMMAND deleteSession()
tester_1 | [0-0] 2020-09-28T07:55:16.119Z INFO webdriver: [DELETE] http://selenium:4444/wd/hub/session/82d59567606b7f101da8650600e7dd00
selenium_1 | 07:55:16.196 INFO [ActiveSessions$1.onStop] - Removing session 82d59567606b7f101da8650600e7dd00 (org.openqa.selenium.chrome.ChromeDriverService)
tester_1 | [0-0] FAILED in chrome - /test/specs/basic.js
tester_1 | 2020-09-28T07:55:16.299Z INFO #wdio/cli:launcher: Run onComplete hook
tester_1 |
tester_1 | "spec" Reporter:
tester_1 | ------------------------------------------------------------------
tester_1 | [chrome 85.0.4183.83 linux #0-0] Spec: /usr/src/app/test/specs/basic.js
tester_1 | [chrome 85.0.4183.83 linux #0-0] Running: chrome (v85.0.4183.83) on linux
tester_1 | [chrome 85.0.4183.83 linux #0-0] Session ID: 82d59567606b7f101da8650600e7dd00
tester_1 | [chrome 85.0.4183.83 linux #0-0]
tester_1 | [chrome 85.0.4183.83 linux #0-0] test app
tester_1 | [chrome 85.0.4183.83 linux #0-0] ✖ should have the right title
tester_1 | [chrome 85.0.4183.83 linux #0-0]
tester_1 | [chrome 85.0.4183.83 linux #0-0] 1 failing (1.6s)
tester_1 | [chrome 85.0.4183.83 linux #0-0]
tester_1 | [chrome 85.0.4183.83 linux #0-0] 1) test app should have the right title
tester_1 | [chrome 85.0.4183.83 linux #0-0] unknown error: unknown error: net::ERR_SSL_PROTOCOL_ERROR
tester_1 | (Session info: chrome=85.0.4183.83)
tester_1 | [chrome 85.0.4183.83 linux #0-0] at <Jasmine>
tester_1 | [chrome 85.0.4183.83 linux #0-0] at processTicksAndRejections (internal/process/task_queues.js:97:5)
tester_1 | [chrome 85.0.4183.83 linux #0-0] at UserContext.<anonymous> (/usr/src/app/test/specs/basic.js:3:17)
Some hints:
when I call curl http://app:3000 from tester or selenium container I receive the HTML as expected.
when I navigate to google in the test, I receive the google code
Thank you for your time!
I am starting to use Appium and I am trying to open up the simulated device. However, I do not understand this message. It starts getting looped again and again. What am I missing for this one?
Launching Appium with command: '/Applications/Appium.app/Contents/Resources/node/bin/node' appium/build/lib/main.js --debug-log-spacing --automation-name "Appium" --platform-name "Android" --platform-version "5.1" --app "/Users/wangeltamang/Downloads/AUT.apk" --avd "Nexus_S_API_19"
[Appium] Welcome to Appium v1.5.3
[Appium] Non-default server args:
[Appium] debugLogSpacing: true
[Appium] platformName: 'Android'
[Appium] platformVersion: '5.1'
[Appium] automationName: 'Appium'
[Appium] app: '/Users/wangeltamang/Downloads/AUT.apk'
[Appium] avd: 'Nexus_S_API_19'
[Appium] Deprecated server args:
[Appium] --platform-name => --default-capabilities '{"platformName":"Android"}'
[Appium] --platform-version => --default-capabilities '{"platformVersion":"5.1"}'
[Appium] --automation-name => --default-capabilities '{"automationName":"Appium"}'
[Appium] --app => --default-capabilities '{"app":"/Users/wangeltamang/Downloads/AUT.apk"}'
[Appium] --avd => --default-capabilities '{"avd":"Nexus_S_API_19"}'
[Appium] Default capabilities, which will be added to each request unless overridden by desired capabilities:
[Appium] platformName: 'Android'
[Appium] platformVersion: '5.1'
[Appium] automationName: 'Appium'
[Appium] app: '/Users/wangeltamang/Downloads/AUT.apk'
[Appium] avd: 'Nexus_S_API_19'
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
[HTTP] --> GET /wd/hub/status {}
[MJSONWP] Calling AppiumDriver.getStatus() with args: []
[MJSONWP] Responding to client with driver.getStatus() result: {"build":{"version":"1.5.3"...
This part of the log is showing Appium being launched. It starts off with showing the used command, then moves on to show the DesiredCapabilities for your launch.
Launching Appium with command: '/Applications/Appium.app/Contents/Resources/node/bin/node' appium/build/lib/main.js --debug-log-spacing --automation-name "Appium" --platform-name "Android" --platform-version "5.1" --app "/Users/wangeltamang/Downloads/AUT.apk" --avd "Nexus_S_API_19"
[Appium] Welcome to Appium v1.5.3
[Appium] Non-default server args:
[Appium] debugLogSpacing: true
[Appium] platformName: 'Android'
[Appium] platformVersion: '5.1'
[Appium] automationName: 'Appium'
[Appium] app: '/Users/wangeltamang/Downloads/AUT.apk'
[Appium] avd: 'Nexus_S_API_19'
[Appium] Deprecated server args:
[Appium] --platform-name => --default-capabilities '{"platformName":"Android"}'
[Appium] --platform-version => --default-capabilities '{"platformVersion":"5.1"}'
[Appium] --automation-name => --default-capabilities '{"automationName":"Appium"}'
Below that you can see the GET command to check for the server status, as well as the response from the command (which is the section that's looping).
[HTTP] --> GET /wd/hub/status {}
[MJSONWP] Calling AppiumDriver.getStatus() with args: []
[MJSONWP] Responding to client with driver.getStatus() result: {"build":{"version":"1.5.3"...
Also you should know about response codes in appium logs like
0 for success
7 NoSuchElement etc.
https://github.com/SeleniumHQ/selenium/wiki/JsonWireProtocol
After reading this webpage you will be able to easily understand appium logs
I am assuming that you are working with the GUI from the format of you appium log.
Make sure you select the "Prelaunch Application" in the General Settings
See screenshot