e2e test doesn't work with multiCapabilities #975

PhilippSoehnlein · 2016-06-01T12:16:09Z

The main goal I try to achieve is to run the e2e tests of an angular-cli generated app on multiple browsers which currently fails because as soon as I add a second browser I get Unexpected token import errors when I run tests.

Please provide us with the following information:

OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Mac OS X El Capitan (10.11.4).

Versions. Please run ng --version. If there's nothing outputted, please
run in a Terminal:
node --version
And paste the result here.

$ ng --version
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.5
node: 5.9.1
os: darwin x64

$ node --version
v5.9.1

Repro steps. Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

Create an app with angular-cli: ng new testfoo
Change protractor.conf.js like this to make tests run in multiple browsers:

diff --git a/config/protractor.conf.js b/config/protractor.conf.js
index 57f4f87..76b4df8 100644
--- a/config/protractor.conf.js
+++ b/config/protractor.conf.js
@@ -6,9 +6,10 @@ exports.config = {
   specs: [
     '../e2e/**/*.e2e.ts'
   ],
-  capabilities: {
-    'browserName': 'chrome'
-  },
+  multiCapabilities: [
+    { 'browserName': 'chrome' },
+    { 'browserName': 'firefox' }
+  ],
   directConnect: true,
   baseUrl: 'http://localhost:4200/',
   framework: 'jasmine',

The log given by the failure. Normally this include a stack trace and some more information.

$ ng serve &
$ ng e2e
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.

> testfoo@0.0.0 pree2e /Users/u1235/tmp/angularclitest/testfoo
> webdriver-manager update

selenium standalone is up to date.
chromedriver is up to date.

> testfoo@0.0.0 e2e /Users/u1235/tmp/angularclitest/testfoo
> protractor "config/protractor.conf.js"

[14:02:58] I/launcher - Running 2 instances of WebDriver
[14:02:59] I/testLogger -
------------------------------------

[14:02:59] I/testLogger - [chrome #01] PID: 4694
[chrome #01] Specs: /Users/u1235/tmp/angularclitest/testfoo/e2e/app.e2e.ts
[chrome #01]
[chrome #01] [14:02:58] I/direct - Using ChromeDriver directly...
[chrome #01] [14:02:59] I/runnerCli - Unexpected token import

[14:02:59] I/testLogger -

[14:02:59] E/launcher - Runner process exited unexpectedly with error code: 1
[14:02:59] I/launcher - 1 instance(s) of WebDriver still running
[14:03:00] I/testLogger -
------------------------------------

[14:03:00] I/testLogger - [firefox #11] PID: 4695
[firefox #11] Specs: /Users/u1235/tmp/angularclitest/testfoo/e2e/app.e2e.ts
[firefox #11]
[firefox #11] [14:02:58] I/direct - Using FirefoxDriver directly...
[firefox #11] [14:03:00] I/runnerCli - Unexpected token import

[14:03:00] I/testLogger -

[14:03:00] E/launcher - Runner process exited unexpectedly with error code: 1
[14:03:00] I/launcher - 0 instance(s) of WebDriver still running
[14:03:00] I/launcher - chrome #01 failed with exit code: 1
[14:03:00] I/launcher - firefox #11 failed with exit code: 1
[14:03:00] I/launcher - overall: 2 process(es) failed to complete
[14:03:00] E/launcher - Process exited with error code 100

Some end-to-end tests failed, see above.

5. Mention any other details that might be useful.

Interestingly it works if multiCapabilities is used with only one browser, no matter which.

The text was updated successfully, but these errors were encountered:

raymondkarstensen · 2016-06-06T09:37:41Z

Had the same problem, but fixed it by adding the following to protractor.conf.js
onPrepare: function () { require('ts-node').register({ project: 'e2e' }); }

PhilippSoehnlein · 2016-06-07T06:45:34Z

@raymondkarstensen Thanks, that works for me.

filipesilva · 2016-06-07T15:49:29Z

How odd... we already have require('ts-node').register({ project: 'e2e' }); in the beforeLaunch callback, which according to https://github.com/angular/protractor/blob/master/docs/referenceConf.js#L223-L227 should run before onPrepare. I need to investigate this further.

raymondkarstensen · 2016-06-07T16:46:10Z

Actually I moved it from beforeLaunch to onPrepare.

chrischiang410 · 2016-10-24T04:01:04Z

Had the same problem, too.
After moving require('ts-node').register({ project: 'e2e' }) from beforeLaunch to onPrepare, Protractor worked fine with multiple browser finally!
Thanks @raymondkarstensen

aniruddhadas9 · 2017-03-16T19:37:13Z

moving from onPrepare is also worked for me. More over I am using sauce lab to test my test cases and now its able to connect to sauce lab and start testing.

@angular/cli: 1.0.0-rc.1
node: 6.9.1
os: darwin x64

onPrepare() {
jasmine.getEnv().addReporter(new SpecReporter({ spec: { displayStacktrace: true } }));
require('ts-node').register({
project: 'e2e/tsconfig.e2e.json'
});
}

kevcjones-archived · 2017-03-30T16:02:58Z

I can confirm using browserstack local + multiCapabilities i had the same issue. I turned off direct connect too from some console complaining it did.

@angular/cli 1.0.0
node: 6.9.5
El Capitan 10.11.5

Same as @raymondkarstensen, moving to the Prepare stage worked a treat. Is there a consequence to this?

micahwood · 2017-05-09T16:47:49Z

It looks like this is the key reason for needing it in onPrepare when using multiCapabilities.

If multiple capabilities are being run, this will run once per capability

https://github.com/angular/protractor/blob/master/lib/config.ts#L407

beforeLaunch only runs once and only once, so I'm guessing each capability requires it's own typescript compiler.

@raymondkarstensen

Thanks to @raymondkarstensen for this solution. Fix angular#975

@raymondkarstensen

Thanks to @raymondkarstensen for this solution. Fix #975

@raymondkarstensen

Thanks to @raymondkarstensen for this solution. Fix #975

@raymondkarstensen

Thanks to @raymondkarstensen for this solution. Fix #975

@raymondkarstensen

Thanks to @raymondkarstensen for this solution. Fix angular#975

angular-automatic-lock-bot · 2019-09-07T02:41:39Z

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

PhilippSoehnlein changed the title ~~e2e test don't work with multiCapabilities~~ e2e test doesn't work with multiCapabilities Jun 1, 2016

filipesilva added type: bug/fix P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent labels Jun 2, 2016

filipesilva self-assigned this Jun 7, 2016

hansl modified the milestone: RC1 Nov 11, 2016

rodrigopandini mentioned this issue Feb 23, 2017

fix: e2e tests cannot run rolandjitsu/angular-lab#63

Closed

hansl removed this from the RC1 milestone Mar 16, 2017

filipesilva added a commit to filipesilva/angular-cli that referenced this issue May 10, 2017

fix(@angular/cli): allow e2e multi capabilities

c413534

Thanks to @raymondkarstensen for this solution. Fix angular#975

filipesilva mentioned this issue May 10, 2017

fix(@angular/cli): allow e2e multi capabilities #6255

Merged

filipesilva closed this as completed in #6255 May 10, 2017

filipesilva added a commit that referenced this issue May 10, 2017

fix(@angular/cli): allow e2e multi capabilities

cfdbb67

Thanks to @raymondkarstensen for this solution. Fix #975

sumitarora pushed a commit that referenced this issue May 15, 2017

fix(@angular/cli): allow e2e multi capabilities

4f48be0

Thanks to @raymondkarstensen for this solution. Fix #975

sumitarora pushed a commit that referenced this issue May 18, 2017

fix(@angular/cli): allow e2e multi capabilities

8a7f6dd

Thanks to @raymondkarstensen for this solution. Fix #975

dond2clouds pushed a commit to d2clouds/speedray-cli that referenced this issue Apr 23, 2018

fix(@angular/cli): allow e2e multi capabilities

74c809a

Thanks to @raymondkarstensen for this solution. Fix angular#975

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

e2e test doesn't work with multiCapabilities #975

e2e test doesn't work with multiCapabilities #975

PhilippSoehnlein commented Jun 1, 2016

Please provide us with the following information:

5. Mention any other details that might be useful.

raymondkarstensen commented Jun 6, 2016

PhilippSoehnlein commented Jun 7, 2016

filipesilva commented Jun 7, 2016

raymondkarstensen commented Jun 7, 2016

chrischiang410 commented Oct 24, 2016

aniruddhadas9 commented Mar 16, 2017

kevcjones-archived commented Mar 30, 2017

micahwood commented May 9, 2017

angular-automatic-lock-bot bot commented Sep 7, 2019

e2e test doesn't work with multiCapabilities #975

e2e test doesn't work with multiCapabilities #975

Comments

PhilippSoehnlein commented Jun 1, 2016

Please provide us with the following information:

5. Mention any other details that might be useful.

raymondkarstensen commented Jun 6, 2016

PhilippSoehnlein commented Jun 7, 2016

filipesilva commented Jun 7, 2016

raymondkarstensen commented Jun 7, 2016

chrischiang410 commented Oct 24, 2016

aniruddhadas9 commented Mar 16, 2017

kevcjones-archived commented Mar 30, 2017

micahwood commented May 9, 2017

angular-automatic-lock-bot bot commented Sep 7, 2019