Skip to content
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.

unable to provide/set element id properly to selectPickerWheelValue #18

Open
christian-bromann opened this issue Feb 25, 2019 · 4 comments

Comments

@christian-bromann
Copy link
Contributor

From @LayMuiToh on February 25, 2019 12:24

[//]: # 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:**v.4.14.1

  • Mode: [Standalone mode or WDIO Testrunner: wdio testrunner

  • **If WDIO Testrunner, running sync/async:**sync

  • Node.js version: v10.15.1

  • **NPM version:**6.4.1

  • **Browser name and version:**NA (mobile native)

  • Platform name and version: iOS 10.3.1

  • Additional wdio packages used (if applicable): [e.g. @wdio/spec reporter, @wdio/selenium-standalone service]

Config of WebdriverIO

exports.config = {

    //
    // ==================
    // 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/**/**'
    ],
    // define specific suites
    suites: {
        
    // 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.10.1',
        platformVersion: '10.3.1',
        platformName: 'iOS',
        deviceName: 'iPhone Simulator',
        udid: '03AE5EA1-DB79-40F2-A365-677B710B5837',
        app: '/Users/tohlaymui/Library/Developer/Xcode/DerivedData/performance_analyst-exzmnafxweexfvdwtpbkbseqplub/Build/Products/Debug-iphonesimulator/performance_analyst.app',
        bundleId: 'ai.telepathy.performanceanalyst-dev',
        automationName: 'XCUITests',
        noReset: false,
        usePrebuiltWDA: true,
        newCommandTimeout: 7000,
        printPageSourceOnFindFailure: true,
       
    }],        
    //
    // ===================
    // Test Configurations
    // ===================
    // Define all options that are relevant for the WebdriverIO instance here
    //
    // By default WebdriverIO commands are executed in a synchronous way using
    // the wdio-sync package. If you still want to run your tests in an async way
    // e.g. using promises you can set the sync option to false.
    sync: true,
    //
    // Level of logging verbosity: silent | verbose | command | data | result | error
    logLevel: 'verbose',
    //
    // Enables colors for log output.
    coloredLogs: true,
    //
    // Warns when a deprecated command is used
    deprecationWarnings: true,
    //
    // 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,
    //
    // Saves a screenshot to a given path if a command fails.
    screenshotPath: './errorShots/',
    //
    // 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,
    //
    // Initialize the browser instance with a WebdriverIO plugin. The object should have the
    // plugin name as key and the desired plugin options as properties. Make sure you have
    // the plugin installed before running any tests. The following plugins are currently
    // available:
    // WebdriverCSS: https://github.com/webdriverio/webdrivercss
    // WebdriverRTC: https://github.com/webdriverio/webdriverrtc
    // Browserevent: https://github.com/webdriverio/browserevent
    plugins: {
        'wdio-screenshot': {},
        'wdio-native-app-compare': {
            baselineFolder: '.dist/image-compare/baseline',
            screenshotPath: '.dist/image-compare/screenshots',
            autoSaveBaseline: true,
            blockOutStatusBar: true,
            blockOutIphoneXBottomBar: true,
            blockOutNavigationBar: true,
            debug: true,

            // See Options for more options
            //..
          },
    },
    //
    // 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: {
        args: {
            address: '127.0.0.1',
            commandTimeout: '11000',
            sessionOverride: true,
            debugLogSpacing: true,
            platformVersion: '10.3.1',
            platformName: 'iOS',
            showIosLog: true,
            deviceName: 'iPhone 6s',
            nativeInstrumentsLib: true,
            app: '/Users/tohlaymui/Library/Developer/Xcode/DerivedData/performance_analyst-exzmnafxweexfvdwtpbkbseqplub/Build/Products/Debug-iphonesimulator/performance_analyst.app',
        },
    },
    // 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: http://webdriver.io/guide/testrunner/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: http://webdriver.io/guide/reporters/dot.html
    // reporters: ['dot'],
    //
    // Options to be passed to Mocha.
    // See the full list at http://mochajs.org/
    mochaOpts: {
        ui: 'bdd',
        timeout:99999999,
        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) {
        var chai = require('chai');
        global.expect = chai.expect;
        chai.Should();
    },
    /**
     * Hook that gets executed before the suite starts
     * @param {Object} suite suite details
     */
    beforeSuite: function (suite) {
    },
    /**
     * 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 before a test (in Mocha/Jasmine) or a step (in Cucumber) starts.
     * @param {Object} test test details
     */
    beforeTest: function (test) {
    },
    //
    /**
     * 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) {
    },
    /**
     * 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) {
    },
    /**
     * 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) {
    },
    /**
     * 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
     */
    onComplete: function (exitCode, config, capabilities) {
    },
    //
    // Cucumber specific hooks
    beforeFeature: function (feature) {
    },
    beforeScenario: function (scenario) {
    },
    beforeStep: function (step) {
    },
    afterStep: function (stepResult) {
    },
    afterScenario: function (scenario) {
    },
    afterFeature: function (feature) {
    }
};

Describe the bug
An unknown server-side error occurred while processing the command. Original error: Element id is expected to be set for selectPickerWheelValue method

code snippet to call the selectPickerWheel:
browser.execute('mobile: selectPickerWheelValue',
{ element: MoreFilters.picker.ELEMENT, order: 'next', offset: 0.5});

import Page from './Page';

const SELECTORS = {
   
    IOS_PICKERWHEEL: '~Picker',
    DONE: '~Done',
   
};

class MoreFilters extends Page {

    /* 
    ** Define elements
    */
    
    get picker()  { return $(SELECTORS.IOS_PICKERWHEEL); }
    get done()  { return $(SELECTORS.DONE); }

 it('should able to tap on the More Filters and go to the More Filters Page', () => {
        Results.morefilters.waitForVisible() &&
        Results.morefilters.click();

        if (MoreFilters.filter_by_date.waitForVisible()) {
          const filter_by_date_x = browser.getLocation('~Filter by Date', 'x');
          const filter_by_date_y = browser.getLocation('~Filter by Date', 'y');
          browser.execute('mobile: tap', 
          { element: MoreFilters.filter_by_date, x: filter_by_date_x, y: filter_by_date_y});
          
          if (MoreFilters.picker.waitForVisible()) {
            browser.execute('mobile: selectPickerWheelValue', 
            { element: MoreFilters.picker.ELEMENT, order: 'next', offset: 0.5});
 
            MoreFilters.done.waitForVisible() && 
            MoreFilters.done.click();
          }
        } 
    });
      

To Reproduce
Steps to reproduce the behavior:

[Include code or an example repository that can easily be set up]

Expected behavior
it should able to select the picker UI element value.

Log
If applicable, add logs to help explain your problem.
https://gist.github.com/LayMuiToh/2a36e54b6832394ee3daa9e0557307f4

Additional context
Add any other context about the problem here.

Please use the correct markdown

Copied from original issue: webdriverio/webdriverio#3617

@christian-bromann
Copy link
Contributor Author

Moving to v4 repo. We don't actively fix issues for v4 anymore. However we are happy to merge provided fixes and release new versions.

@LayMuiToh
Copy link

LayMuiToh commented Feb 25, 2019

Sure however at the moment appium has an issue with WebdriverIO v5 thus I am unable to upgrade

rhysd/wdio-appium-service#12

@christian-bromann
Copy link
Contributor Author

@LayMuiToh maybe consider help to port the service 😉

@LayMuiToh
Copy link

Hi Christian, you mean the appium service? I will give it a try. any tips to get started?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants