Add DirectConnect Support for Firefox 51+

[theandrewlane]

Currently directConnect can't be used with FF 48+. FF 51 was however released today (January 24th) and should now be able to fully support Protractor.

The two other issues impacting directConnect have been fixed:

• Fixed: Selenium bug #3115
• Fixed: FF bug #1297551

This will also require a Selenium 3.0.2 release

Current Working FF configuration with directConnect:

Browser: FF 47.0.2
Protractor: 5.0.0
Node: 7.4.0
OS: Win 7 Enterprise

 exports.config = {
    directConnect: true,
    process.env.BASE_URL,
    specs: ['e2e/tests/**/*-e2e.js'],
    capabilities: {
      browserName: 'firefox', //Allow execution against different browsers.
      marionette: false,
      shardTestFiles: !!process.env.SHARD_TESTS,
      maxInstances: process.env.E2E_MAX_INSTANCES || 2,
      allScriptsTimeout: 35000,
      pageLoadingStrategy: 'eager',
    },

    framework: 'jasmine2',

    plugins: [
      {path: path.resolve(__dirname) + '/protractor-plugins/coverage-plugin.js'},
      {path: path.resolve(__dirname) + '/protractor-plugins/reset-plugin.js'},
      {path: path.resolve(__dirname) + '/protractor-plugins/screenshot-plugin.js'}
    ],

    params: {
      disableAnimations: true,
      sharding: false,
      junitFileName: 'TESTS-protractor.xml'
    },

    // Options to be passed to Jasmine-node.
    jasmineNodeOpts: {
      showColors: true,
      defaultTimeoutInterval: 30000,
      isVerbose: true,
      print() {
      } //disable and use jasmine-spec-reporter instead
    },
    onPrepare() {
      const jasmineEnv = jasmine.getEnv();
      browser.driver.manage().window().setSize(1280, 1024);
      }

      jasmineEnv.addReporter(new jasmineReporters.JUnitXmlReporter({
        consolidateAll: true,
        filePrefix: protractorConfig.params.junitFileName,
        savePath: 'results'
      }));

      jasmineEnv.addReporter(new SpecReporter({
        displayStacktrace: 'summary',
        displayPendingSpec: true,
        displaySpecDuration: true
      }));
      
      require('jasmine-expect');
    }
  };

[heathkit]

Please see #3823 and #3953. Support for Firefox 51+ with directConnect will be in the next release. For those not using directConnect, until selenium standalone 3.0.2 is released, 3.0.0-beta4 will work.

[heathkit]

We're hoping for Monday. You should be able to test on Firefox 51 using selenium standalone until then. You can see how our CircleCI config does it for an example: https://github.com/angular/protractor/blob/master/circle.yml

…

On Tue, Jan 24, 2017 at 3:18 PM, Andrew Lane ***@***.***> wrote: @mgiambalvo <https://github.com/mgiambalvo> How soon can we expect the next release? :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4005 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAlR5VQ4xIPeZm3eAKOkgzx5Ayn6b4qks5rVobhgaJpZM4Ls3sy> .

[joeydaowang]

I am using Protractor 5.1.1 + webdriver-manager 12.0.2, directConnect true doesn't work with FF 51.0.1. I still have connection timeout issue.
Here is partial of my config file

    capabilities: {
        'browserName': 'firefox',
        marionette: false,
        shardTestFiles: true,
        maxInstances: 3,
    },
    baseUrl: 'http://localhost:8000',
    framework: 'jasmine2',
    jasmineNodeOpts: {
        defaultTimeoutInterval: 120000,
        realtimeFailure: true
    },
    directConnect: true,

Did I do something wrong here?

[spac-valentin]

I am having the exact same issue as @joeydaowang, using selenium-server-standalone-3.2.0. Any news on this?

[ngie-mp]

same issue as @joeydaowang; protractor 5.1.1, webdriver-manager 12.02 and FF 51.0.1.

[glepretre]

@joeydaowang @ngie-mp I think you should enable marionette (default, true) when running Firefox 48+, but this might not fix your issue though

[joeydaowang]

@glepretre I tried with marionette enabled. It didn't help.
Today tried with FF 52, the same issue still.
@mgiambalvo any idea what I have done wrong? thanks

[rahulmr]

@joeydaowang me too having same issue with latest protractor version and latest webdriver

[heathkit]

See the newest issue with directConnect here: #4253

If you're on FF52 and Selenium 3, you no longer need to set marionette (it's true by default).