Hi Team,
I am facing below issue while running my test on mac-mini device for IOS simulator.
[0-0] 2022-05-29T18:48:13.318Z WARN @wdio/utils:shim: You are running tests with @wdio/sync which will be discontinued starting Node.js v16.Read more on https://github.com/webdriverio/webdriverio/discussions/6702RROR webdriver: Request failed with status undefined due to TimeoutError: Timeout awaiting 'request' for 120000ms when running "http://localhost:4723/session" with method "POST" and args "{"capabilities":{"alwaysMatch":{"platformName":"iOS","noReset":false,"fullReset":true,"automationName":"XCUITest","deviceName":"iPhone 13","platformVersion":"15.4","app":"/Users/builder/Library/Developer/Xcode/DerivedData/Runner-edaimyiflreloheqntgnhkmwcclv/Build/Products/Debug-iphonesimulator/Runner.app","appWaitDuration":20000,"newCommandTimeout":90000,"webviewConnectTimeout":20000,"fullContextList":true,"autoAcceptAlerts":true,"chromedriverExecutable":"","chromeOptions":{"w3c":false,"args":["--disable-popup-blocking"]}},"firstMatch":[{}]},"desiredCapabilities":{"platformName":"iOS","noReset":false,"fullReset":true,"automationName":"XCUITest","deviceName":"iPhone 13","platformVersion":"15.4","app":"/Users/builder/Library/Developer/Xcode/DerivedData/Runner-edaimyiflreloheqntgnhkmwcclv/Build/Products/Debug-iphonesimulator/Runner.app","appWaitDuration":20000,"newCommandTimeout":90000,"webviewConnectTimeout":20000,"fullContextList":true,"autoAcceptAlerts":true,"chromedriverExecutable":"","chromeOptions":{"w3c":false,"args":["--disable-popup-blocking"]}}}"
If I run same test on mac-pro, it is working perfectly.
The difference I am seeing:
Mac-Mini- Runner.app is getting installed correctly but it is not launching due to above mentioned error.
Mac-Pro- Runner.app is getting installed but it has the different app name instead of “Runner” + I see “Webdriver Agent” is also get installed in my simulator + app is launching correctly + my tests are passing.
My IOS config for the same is:
import config from './wdio.conf';
import PlatformInfo from './platform.info';
// Appium capabilities
config.capabilities = [
{
platformName: 'iOS',
noReset: false,
fullReset: true,
maxInstances: 1,
automationName: 'XCUITest',
deviceName: PlatformInfo.deviceName(),
platformVersion: PlatformInfo.platformVersion(),
app: PlatformInfo.appName(),
appWaitDuration: 20000,
newCommandTimeout: 90000,
webviewConnectTimeout: 20000,
fullContextList: true,
autoAcceptAlerts: true,
chromedriverExecutable: '',
chromeOptions: {
'w3c': false,
'args': [
'--disable-popup-blocking',
],
},
},
];
config.cucumberOpts.tagExpression = '@iosApp';// pass tag to run tests specific to ios
exports.config = config;
My wdio.config for the same is:
import ADBHelper from ‘…/src/utils/adbHelper’;
const platformName = process.env.PLATFORM_NAME;
const config = {
//
// ====================
// Runner Configuration
// ====================
//
// WebdriverIO allows it to run your tests in arbitrary locations (e.g. locally or
// on a remote machine).
runner: 'local',
//
// ==================
// Specify Test Files
// ==================
// Define which test specs should run. The pattern is relative to the directory
// from which `wdio` was called.
//
// The specs are defined as an array of spec files (optionally using wildcards
// that will be expanded). The test for each spec file will be run in a separate
// worker process. In order to have a group of spec files run in the same worker
// process simply enclose them in an array within the specs array.
//
// If you are calling `wdio` from an NPM script (see https://docs.npmjs.com/cli/run-script),
// then the current working directory is where your `package.json` resides, so `wdio`
// will be called from there.
//
specs: [
'./test/features/*.feature',
],
// Patterns to exclude.
exclude: [
// 'path/to/excluded/files'
],
//
// ============
// Capabilities
// ============
// Define your capabilities here. WebdriverIO can run multiple capabilities at the same
// time. Depending on the number of capabilities, WebdriverIO launches several test
// sessions. Within your capabilities you can overwrite the spec and exclude options in
// order to group specific specs to a specific capability.
//
// First, you can define how many instances should be started at the same time. Let's
// say you have 3 different capabilities (Chrome, Firefox, and Safari) and you have
// set maxInstances to 1; wdio will spawn 3 processes. Therefore, if you have 10 spec
// files and you set maxInstances to 10, all spec files will get tested at the same time
// and 30 processes will get spawned. The property handles how many capabilities
// from the same test should run tests.
//
maxInstances: 10,
//
// If you have trouble getting all important capabilities together, check out the
// Sauce Labs platform configurator - a great tool to configure your capabilities:
// https://docs.saucelabs.com/reference/platforms-configurator
//
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: 5,
platformName: '',
noReset: false,
fullReset: false,
automationName: '',
deviceName: '',
platformVersion: '',
app: '',
appWaitDuration: 20000,
newCommandTimeout: 12000,
webviewConnectTimeout: 10000,
fullContextList: false,
autoAcceptAlerts: true,
chromedriverExecutable: '',
chromeOptions: {
'w3c': false,
'args': [
'--no-sandbox',
],
},
// 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'],
}],
//
// ===================
// Test Configurations
// ===================
// Define all options that are relevant for the WebdriverIO instance here
//
// Level of logging verbosity: trace | debug | info | warn | error | silent
logLevel: 'trace',
//
// Set specific log levels per logger
// loggers:
// - webdriver, webdriverio
// - @wdio/applitools-service, @wdio/browserstack-service, @wdio/devtools-service, @wdio/sauce-service
// - @wdio/mocha-framework, @wdio/jasmine-framework
// - @wdio/local-runner
// - @wdio/sumologic-reporter
// - @wdio/cli, @wdio/config, @wdio/utils
// Level of logging verbosity: trace | debug | info | warn | error | silent
// logLevels: {
// webdriver: 'info',
// '@wdio/applitools-service': 'info'
// },
//
// If you only want to run your tests until a specific amount of tests have failed use
// bail (default is 0 - don't bail, run all tests).
bail: 0,
//
// Set a base URL in order to shorten url command calls. If your `url` parameter starts
// with `/`, the base url gets prepended, not including the path portion of your baseUrl.
// If your `url` parameter starts without a scheme or `/` (like `some/path`), the base url
// gets prepended directly.
baseUrl: 'http://localhost',
//
// Default timeout for all waitFor* commands.
waitforTimeout: 10000,
//
// Default timeout in milliseconds for request
// if browser driver or grid doesn't send response
connectionRetryTimeout: 120000,
//
// Default request retries count
connectionRetryCount: 3,
//
// Test runner services
// Services take over a specific job you don't want to take care of. They enhance
// your test setup with almost no effort. Unlike plugins, they don't add new
// commands. Instead, they hook themselves up into the test process.
services: [
'appium',
],
appium: {
command: 'appium --chromedriver-executable ./node_modules/appium-chromedriver/chromedriver/mac/chromedriver_mac64_v91.0.4472.101',
},
port: 4723,
path: '/wd/hub',
// Framework you want to run your specs with.
// The following are supported: Mocha, Jasmine, and Cucumber
// see also: https://webdriver.io/docs/frameworks
//
// Make sure you have the wdio adapter package for the specific framework installed
// before running any tests.
framework: 'cucumber',
cucumberOpts: {
backtrace: false,
requireModule: [],
failAmbiguousDefinitions: false,
failFast: false,
ignoreUndefinedDefinitions: false,
name: [],
profile: [],
require: [
'./src/stepDefinitions/*.ts',
],
tagExpression: '@androidApp',
snippetSyntax: undefined,
snippets: true,
source: true,
strict: false,
tagsInTitle: false,
timeout: 50000,
retry: 0,
},
//
// The number of times to retry the entire specfile when it fails as a whole
// specFileRetries: 1,
//
// Delay in seconds between the spec file retry attempts
// specFileRetriesDelay: 0,
//
// Whether or not retried specfiles should be retried immediately or deferred to the end of the queue
// specFileRetriesDeferred: false,
//
// Test reporter for stdout.
// The only one supported by default is 'dot'
// see also: https://webdriver.io/docs/dot-reporter
reporters: [
'spec',
[
'allure',
{
outputDir: './test-report/allure-result/',
disableWebdriverStepsReporting: true,
disableWebdriverScreenshotsReporting: false,
useCucumberStepReporter: true,
},
],
],
//
// Options to be passed to Mocha.
// See the full list at http://mochajs.org/
// mochaOpts: {
// ui: 'bdd',
// timeout: 60000,
// },
//
// =====
// Hooks
// =====
// WebdriverIO provides several hooks you can use to interfere with the test process in order to enhance
// it and to build services around it. You can either apply a single function or an array of
// methods to it. If one of them returns with a promise, WebdriverIO will wait until that promise got
// resolved to continue.
/**
* Gets executed once before all workers get launched.
* @param {Object} config wdio configuration object
* @param {Array.<Object>} capabilities list of capabilities details
*/
// onPrepare: function (config, capabilities) {
// },
/**
* Gets executed before a worker process is spawned and can be used to initialise specific service
* for that worker as well as modify runtime environments in an async fashion.
* @param {String} cid capability id (e.g 0-0)
* @param {[type]} caps object containing capabilities for session that will be spawn in the worker
* @param {[type]} specs specs to be run in the worker process
* @param {[type]} args object that will be merged with the main configuration once worker is initialised
* @param {[type]} execArgv list of string arguments passed to the worker process
*/
// onWorkerStart: function (cid, caps, specs, args, execArgv) {
// },
/**
* Gets executed just before initialising the webdriver session and test framework. It allows you
* to manipulate configurations depending on the capability or spec.
* @param {Object} config wdio configuration object
* @param {Array.<Object>} capabilities list of capabilities details
* @param {Array.<String>} specs List of spec file paths that are to be run
*/
// beforeSession: function (config, capabilities, specs) {
// },
/**
* Gets executed before test execution begins. At this point you can access to all global
* variables like `browser`. It is the perfect place to define custom commands.
* @param {Array.<Object>} capabilities list of capabilities details
* @param {Array.<String>} specs List of spec file paths that are to be run
* @param {Object} browser instance of created browser/device session
*/
// before: function (capabilities, specs) {
// },
/**
* Runs before a WebdriverIO command gets executed.
* @param {String} commandName hook command name
* @param {Array} args arguments that command would receive
*/
// beforeCommand: function (commandName, args) {
// },
/**
* Hook that gets executed before the suite starts
* @param {Object} suite suite details
*/
// beforeSuite: function (suite) {
// },
/**
* Function to be executed before a test (in Mocha/Jasmine) starts.
*/
// beforeTest: function (test, context) {
// },
/**
* Hook that gets executed _before_ a hook within the suite starts (e.g. runs before calling
* beforeEach in Mocha)
*/
// beforeHook: function (test, context) {
// },
/**
* Hook that gets executed _after_ a hook within the suite starts (e.g. runs after calling
* afterEach in Mocha)
*/
// afterHook: function (test, context, { error, result, duration, passed, retries }) {
// },
/**
* Function to be executed after a test (in Mocha/Jasmine).
*/
// afterTest: function(test, context, { error, result, duration, passed, retries }) {
// },
// This code is responsible for taking the screenshot in case of error and attaching it to the report
afterStep(uri, feature, scenario) {
if (scenario.error) {
driver.takeScreenshot();
}
},
/**
* Hook that gets executed after the suite has ended
* @param {Object} suite suite details
*/
// afterSuite: function (suite) {
// },
/**
* Runs after a WebdriverIO command gets executed
* @param {String} commandName hook command name
* @param {Array} args arguments that command would receive
* @param {Number} result 0 - command success, 1 - command error
* @param {Object} error error object if any
*/
// afterCommand: function (commandName, args, result, error) {
// },
/**
* Gets executed after all tests are done. You still have access to all global variables from
* the test.
* @param {Number} result 0 - test pass, 1 - test fail
* @param {Array.<Object>} capabilities list of capabilities details
* @param {Array.<String>} specs List of spec file paths that ran
*/
after() {
if (platformName === 'android') {
ADBHelper.executeADBShellCommand('pm clear com.gelato.api.stage'.split(' '));
ADBHelper.executeADBShellCommand('pm clear com.android.chrome'.split(' '));
}
},
/**
* Gets executed right after terminating the webdriver session.
* @param {Object} config wdio configuration object
* @param {Array.<Object>} capabilities list of capabilities details
* @param {Array.<String>} specs List of spec file paths that ran
*/
// afterSession: function (config, capabilities, specs) {
// },
/**
* Gets executed after all workers got shut down and the process is about to exit. An error
* thrown in the onComplete hook will result in the test run failing.
* @param {Object} exitCode 0 - success, 1 - fail
* @param {Object} config wdio configuration object
* @param {Array.<Object>} capabilities list of capabilities details
* @param {<Object>} results object containing test results
*/
// onComplete(exitCode, config, capabilities, results) {
// generate({
// jsonDir: './reports/json',
// reportPath: './reports/html',
// openReportInBrowser: true,
// });
// },
/**
* Gets executed when a refresh happens.
* @param {String} oldSessionId session ID of the old session
* @param {String} newSessionId session ID of the new session
*/
// onReload: function(oldSessionId, newSessionId) {
// }
};
export default config;
My package.json for the same is:
{
"name": "integration-tests",
"version": "1.0.0",
"description": "Project to run native and browser fro android and ios using cucumber",
"main": "index.js",
"scripts": {
"build": "tsc",
"clean": "rimraf typeScript/",
"clean-build": "npm run clean && npm run build",
"android": "wdio ./config/android.config.ts $PLATFORM_NAME",
"ios": "wdio ./config/ios.config.ts",
"lint": "eslint .",
"pretest": "npm run clean-build",
"test": "npm run app-test",
"report": "allure generate ./test-report/allure-result"
},
"keywords": [
"appium",
"webdriverio",
"typescript",
"mobile automation",
"behaviour driven development",
"bdd",
"webdriverJS",
"gherkin",
"automation testing"
],
"author": "",
"license": "ISC",
"devDependencies": {
"@types/chai": "^4.3.1",
"@wdio/allure-reporter": "^7.19.5",
"@wdio/appium-service": "^7.5.2",
"@wdio/cli": "^7.5.2",
"@wdio/local-runner": "^7.5.2",
"@wdio/mocha-framework": "^7.19.5",
"@wdio/spec-reporter": "^7.5.2",
"@wdio/sync": "^7.5.2",
"allure-commandline": "^2.17.2",
"appium": "^1.22.3",
"carthage": "^1.0.6",
"chai": "^4.3.6",
"dotenv": "^16.0.0",
"eslint": "^7.32.0",
"ios-deploy": "^1.11.4",
"ios-simulator-set-location": "^1.0.0",
"mochawesome": "^7.1.3",
"mochawesome-report-generator": "^6.2.0",
"ts-node": "^10.7.0",
"tslint-to-eslint-config": "^2.12.3",
"typescript": "^4.6.3",
"wdio-cucumberjs-json-reporter": "^4.4.1",
"wdio-spec-reporter": "^0.1.5",
"chromedriver": "^91.0.0",
"webdriverio": "^7.19.5"
},
"dependencies": {
"@cucumber/cucumber": "^8.1.2",
"@types/cucumber": "^7.0.0",
"@wdio/cucumber-framework": "^7.19.5",
"assert": "^2.0.0",
"multiple-cucumber-html-reporter": "^1.20.0",
"tslog": "^3.3.3"
}
}
Can someone please help me out so that I can find what I am missing at my end?
Thanks 