Protractor tests don't actually run but report passing (webpack branch)

[caseyhoward]

1. Linux Mint 17.1

2. angular-cli: 1.0.0-beta.11-webpack.8
   node: 6.5.0
   os: linux x64

3. Ran "npm init" then "ng init" in a new directory.
   Added the following test to e2e/app.e2e-spec.ts:

   it('should blow up', () => {
     page.navigateTo();
     expect(page.getParagraphText()).toEqual('app doesn\'t work!');
   });

   Ran "npm start" in one tab and "npm e2e" in another

4. The error is that there is no error. The test I added should have failed.

$ npm run e2e

> blah@0.0.0 pree2e /home/.../blah
> webdriver-manager update

[normal looking chrome driver output]

> blah@0.0.0 e2e /home/...
> protractor

[12:16:55] I/direct - Using ChromeDriver directly...
[12:16:55] I/launcher - Running 1 instances of WebDriver
Spec started

  blah App
    ✓ should display message saying app works
    ✓ should blow up

Executed 2 of 2 specs SUCCESS in 0.025 sec.
[12:16:56] I/launcher - 0 instance(s) of WebDriver still running
[12:16:56] I/launcher - chrome #01 passed

1. It appears that it isn't doing anything at all. No matter how many steps you add to your test in just exits immediately.

[kv113813]

I do have similar issue with Ubuntu + selenium, protractor setup with headless chrome. It passes all the test cases where many shows up failed in other windows/MAC setups and also passes in fact intensionally made failed test cases.

Fixed with protractor 4.0.5, make an update or revert to 3

[filipesilva]

Fixed in #2054

[angular-automatic-lock-bot]

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.}