webdriverio v5 didn't run the automation on the mobile device

LayMuiToh commented 5 years ago

[//]: # NOTE: This repository only maintains packages that are listed in the Readme. Please make sure that your issue is directly caused by one of these packages and if not file an issue in the correct 3rd party package repository.

Environment (please complete the following information):

WebdriverIO version: 5.1.1
Mode: WDIO Testrunner]
**If WDIO Testrunner, running sync
Node.js version:9.1.0
NPM version:6.4.1
Browser name and version: Nil
Platform name and version:iOS 12.1

Additional wdio packages used (if applicable): "@wdio/allure-reporter": "^5.1.0", "@wdio/cli": "^5.1.2", "@wdio/local-runner": "^5.1.1", "@wdio/mocha-framework": "^5.1.0", "@wdio/sync": "^5.1.0", Config of WebdriverIO An example of how you configured WebdriverIO config

exports.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. Notice that, 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/spec/*.js'
],
 // define specific suites
 suites: {
    login: [
        './test/spec/app.login.spec.js'

    ],

    noattr: [
        './test/spec/app.noattr.text.spec.js',
        './test/spec/app.noattr.voice.spec.js'

    ],

},
// 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: 1,
//
// 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.
    browserName: '',
    appiumVersion: '1.9.1',
    platformVersion: '12.1',
    platformName: 'iOS',
    deviceName: 'Lay muis iPhone',
    udid: 'a12510a8c8ec79876d8e10f38da17fb97dc720c3',
    app: '/Usersxxxx/Desktop/xxx/xxx.ipa',
    bundleId: 'xxx-dev',
    automationName: 'XCUITests',
    noReset: true,
    usePrebuiltWDA: true,
    autoLaunch: true,
    newCommandTimeout: 7000
   // autoAcceptAlerts: true
}],        
//
// ===================
// Test Configurations
// ===================
// Define all options that are relevant for the WebdriverIO instance here
//
// Level of logging verbosity: silent | verbose | command | data | result | error
logLevel: 'error',
logDir: './allure-results', 
//
// Enables colors for log output.
coloredLogs: true,
//
// Warns when a deprecated command is used
deprecationWarnings: true,
debug: true,
execArgv: ['--inspect-brk=127.0.0.1:4723'],
// 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 Selenium Grid doesn't send response
connectionRetryTimeout: 90000,
//
// 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: [],//

// Default port for Appium
port: 4723,
maxInstances: 1,
//
// Framework you want to run your specs with.
// The following are supported: Mocha, Jasmine, and Cucumber
// see also: https://webdriver.io/docs/frameworks.html
//
// Make sure you have the wdio adapter package for the specific framework installed
// before running any tests.
framework: 'mocha',
//
// Test reporter for stdout.
// The only one supported by default is 'dot'
// see also: https://webdriver.io/docs/dot-reporter.html
// reporters: ['dot'],
reporters: [['allure', {
    outputDir: 'allure-results',
    disableWebdriverStepsReporting: true,
    disableWebdriverScreenshotsReporting: true,
}]],
//
// Options to be passed to Mocha.
// See the full list at http://mochajs.org/
mochaOpts: {
    ui: 'bdd',
    timeout: 60000,
    compilers: ['js:babel-register'],
},
//
// =====
// 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 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
 */
//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) or a step (in Cucumber) starts.
 * @param {Object} test test details
 */
// beforeTest: function (test) {
// },
/**
 * Hook that gets executed _before_ a hook within the suite starts (e.g. runs before calling
 * beforeEach in Mocha)
 */
// beforeHook: function () {
// },
/**
 * Hook that gets executed _after_ a hook within the suite starts (e.g. runs after calling
 * afterEach in Mocha)
 */
// afterHook: function () {
// },
/**
 * Function to be executed after a test (in Mocha/Jasmine) or a step (in Cucumber) starts.
 * @param {Object} test test details
 */
// afterTest: function (test) {
// },
/**
 * 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: function (result, capabilities, specs) {
// },
/**
 * 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.
 * @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: function(exitCode, config, capabilities, results) {
// }
}

*Describe the bug**

To Reproduce Steps to reproduce the behavior:

[Include code or an example repository that can easily be set up] Login.page.js:

import Page from './Page';

class Login extends Page {

    /* 
    ** Define elements
    */
    get username()  { return $('~email'); }
    get password()  { return $('~password'); }
    get signin()    { return $('~signin'); }

    open() {
        super.open('login');
    }

    login (user, pass) {
        this.username.setValue(user);
        this.password.setValue(pass);

        driver.isKeyboardShown() &&
        driver.hideDeviceKeyboard();

        this.signin.click();
    }

    //isLoggedIn() {
    //    return this.username.waitForDisplayed() && this.password.waitForDisplayed();
   // }
}

export default new Login();

app.login.spec.js:

import { expect } from 'chai';
import  * as loginacct from '../testdata/config/loginacct';
import Login from '../pageobjects/Login.page';
import Main  from '../pageobjects/Main.page';

module.exports = () => {
 describe('Login test', () => {
  beforeEach(() =>  {
    Login.open();
  });

  afterEach(() => {
  });

  it('should login with a correct credential',  () => {
      let validEmail = loginacct.ALL_ACCESS_EMAILID;
      let validPass =  loginacct.ALL_ACCESS_PASSWORD;

      Login.username.waitForDisplayed();
      Login.username.setValue(validEmail);
      Login.password.waitForDisplayed();
      Login.password.setValue(validPass);
      //Login.isLoggedIn &&
      //Login.login(validEmail, validPass);
      /*
      ** Validate it login to Main Page
      */

Page.js:

export default class Page {
    open(name) {
      driver.isLocked() &&
      driver.unlock();
    }
}

Expected behavior node_modules/.bin/wdio wdio.conf.js --suite login test case should run the automation action on the mobile, but the app just launch and exit

Log No log in appium.log although appium is started [Appium] Welcome to Appium v1.9.1 [Appium] Appium REST http interface listener started on 0.0.0.0:4723 Additional context RUNNING 0-0 in - /test/spec/app.login.spec.js

Test Suites: 0 passed, 1 total (0% completed) Time: 🕕 185.67s but nothing is run on the mobile.

Please use the correct markdown

Gilad-Shnoor commented 5 years ago

@LayMuiToh I had a similar issue in android and have a pending pull request to fix it. Can you please see if you get "Error: InvalidSelectorStrategy" from Login.username.setValue(validEmail); to make sure it's the same error?

christian-bromann commented 5 years ago

@LayMuiToh please use proper markdown to format your code otherwise it is impossible to read. Just pasting your wdio config is not useful too. We need appium logs or wdio logs and maybe even better a minimal reproducible example.

Ponyets commented 5 years ago

@LayMuiToh Just update to 5.2.1. I'd consider it as a bug which was fixed yesterday. https://github.com/webdriverio/webdriverio/pull/3226

christian-bromann commented 5 years ago

Closing this then.

flexin777 commented 5 years ago

Hello Where I can take this object driver? I see only browser.

christian-bromann commented 5 years ago

Where I can take this object driver? I see only browser.

Please have a look at our appium boilerplate https://github.com/webdriverio/appium-boilerplate

webdriverio / webdriverio

webdriverio v5 didn't run the automation on the mobile device #3230