Permalink
Commits on Mar 10, 2018
  1. 0.51.1

    samhatoum committed Mar 10, 2018
Commits on Mar 9, 2018
Commits on Feb 8, 2018
  1. Merge pull request #680 from kapman/mocha-specs-fix

    lgandecki committed Feb 8, 2018
    Check for existence of this.options._ before checking length
Commits on Jan 23, 2018
  1. update package.json (#675)

    1996dylanriley authored and samhatoum committed Jan 23, 2018
    This is the latest version of chrome driver which is compatible with the latest version of chrome on windows and in particularly Linux distributions with the official google-chrome-stable package. Take a look here https://sites.google.com/a/chromium.org/chromedriver/downloads
Commits on Jan 8, 2018
  1. 0.51.0

    samhatoum committed Jan 8, 2018
Commits on Jan 7, 2018
Commits on Oct 14, 2017
  1. 0.50.2

    samhatoum committed Oct 14, 2017
Commits on Oct 13, 2017
  1. 0.50.1

    samhatoum committed Oct 13, 2017
  2. update bump browser driver versions (#606)

    dheerajbhaskar authored and samhatoum committed Oct 13, 2017
    * update bump browser driver versions
    
    Especially chrome, since it has a bug "cannot get automation extension” error with chrome version: 57.0.2987.98; reference: http://stackoverflow.com/questions/42806169/cannot-get-automation-extension-error-with-chrome-version-57-0-2987-98
    
    Latest versions sourced from: https://github.com/vvo/selenium-standalone/blob/master/lib/default-config.js
    
    * update versions in package.json
    
    update versions of chromedriver and selenium-standalone
  3. Add multiremote support in browserstack manager (#633)

    naiquevin authored and samhatoum committed Oct 13, 2017
    * Add multiremote support in browserstack manager
    
    * Added multiremote wrapper method
    * Updated killCurrentSession method to mark all sessions associated with
      the first build as completed. (Earlier only the first session was
      being marked).
    
    * Improve Browserstack session cleanup
    
    When cleaning up sessions in browserstack, the 'killCurrentSession'
    function assumed that the current build is the first one of the running
    builds returned by the API. This however may not always be true, eg. if
    the same browserstack account is used for multiple projects, there may
    be more than 1 builds running in parallel.
    
    This commit improves the function by comparing the build name with the
    one specified in desiredCapabilities (set in chimp config file). It's
    however not mandatory to specify the build name, so if it's not
    specified, the original assumption of selecting the first build still
    stands.
    
    In case of multiremote (multiple sessions), it's important to specify
    the build name in desiredCapabilities, multiple sessions will not be
    grouped under one build and hence only one of them will get killed. This
    has been added as a note in the docstring.
  4. Fixes debounce tests

    samhatoum committed Oct 13, 2017
Commits on Oct 11, 2017
  1. fixes #645 (#646)

    hexsprite authored and samhatoum committed Oct 11, 2017
Commits on Oct 9, 2017
Commits on Sep 7, 2017
  1. 0.50.0

    lgandecki committed Sep 7, 2017
Commits on Aug 17, 2017
  1. Merge pull request #639 from tiagolr/master

    lgandecki committed Aug 17, 2017
    allow cucumber `name` option to run specific scenarios
Commits on Jul 14, 2017
  1. 0.49.1

    lgandecki committed Jul 14, 2017
  2. Merge pull request #631 from williamboman/feat/catch-cucumber-errors

    lgandecki committed Jul 14, 2017
    lib/cucumberjs: catch runtime errors