[polymer-test] error with Chrome 66 and 67

[felixzapata]

Hi all, when I launch my tests, the browser window it looks like broken.

polymer test -l chrome --npm

I use "web-component-tester": "^6.6.0" as a devDependency.

I can't see the results of the test on it neither open the console to debug. This happen to another colleague of my team.

This happen with chrome 66 and 67.

My version of Polymer Cli is 1.6.0. It also happens with version 1.7.2.

[TimvdLippe]

Could you provide a reproduction case which allows us to inspect it? This can be a GitHub repo with setup instructions if that is easier for you.

[felixzapata]

hi, I am going to try to describe the configuration because after three hours of work, I've tested dozens of combinations in order to try to fix it. My current configuration is:

• Node 8.0.0 (I was using Node < 8 but I have had to update in order to try with Polymer cli 1.7.x)
• Polymer 1.x
• Polymer cli 1.7.2
• Chrome v67.x
• Inside the package.json of the project:

"devDependencies": {
    "wct-browser-legacy": "^1.0.1",
    "web-component-tester": "^6.6.0"
  }

My colleague has:

• Node < 8
• Polymer 1.x
• Polymer Cli 1.6.x
• Chrome v66.x
• Inside the package.json of the project:

"devDependencies": {
    "web-component-tester": "^6.6.0"
  }

wct-browser-legacy as far as I know it is only need it with Polymer Cli 1.7.x.

We obtain the same error with "web-component-tester": "^6.5.0".

We run the tests with:

polymer test -l chrome --npm
polymer test -l firefox --npm (the only problem with firefox is that there is no output of the console lines, but the rest it is ok)

We did not not have this problem a few days ago and we have not made any changes in our platform related with the versions of the libraries related with the tests.

I do not know if it is related with the Chrome driver. Now, it is supposed that it launches Chrome driver 2.37 but the error is the same.

[TimvdLippe]

Polymer 1.x

I do not think you should be testing with the --npm flag, as Polymer 1 still used HTML imports and Bower. You can test this yourself by using polymer serve and inspect the test page yourself

[felixzapata]

No, I can't. We have our tests inside an application (like for example the tests inside the Polymer News) but we do not serve our application with Polymer serve.

The --npm flag works for us with Polymer 1.x.. Our tests were working without problems in the browsers using this flag.

The tests works on terminal but if you need to stop the browser to check something, or show something via console, the browser is broken.

I am sure that with Chrome 65 I had not this problem.

[felixzapata]

I'm going to try to reproduce the error using the same configuration with the tests inside of the Polymer News project (with a Polymer 1.x version).

[felixzapata]

Instead of the Polymer News, I've run the tests of the version with Polymer 1.x of the Polymer Starter Kit (version 2.2.0):

polymer test -l chrome --npm -p

I've modified the package.json file adding:

"wct-browser-legacy": "^1.0.1",
"web-component-tester": "^6.6.0"

And then, in test/index.html, I've replaced <script src="../bower_components/web-component-tester/browser.js"></script> with <script src="../node_modules/web-component-tester/browser.js"></script>.

[felixzapata]

It also happens with the master branch (Polymer 3.x) of Polymer Starter Kit.

and with version 3.2.1 of Polymer Starter Kit (with Polymer 2.x):

Both tests, just a fresh install and running the tests via command line:

polymer test -l chrome -p

[felixzapata]

@TimvdLippe any news about this issue?

[TimvdLippe]

I am unable to reproduce this issue, so sadly cant provide any help atm :(

…

On Fri, 15 Jun 2018, 07:46 Félix Zapata, ***@***.***> wrote: @TimvdLippe <https://github.com/TimvdLippe> any news about this issue? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#509 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFrDb8UC_nw2Z4g1ZwCaMEi-RxkRiVGPks5t80pSgaJpZM4UkHh_> .

[felixzapata]

but it happens with fresh install of the projects and Chromes 66 and 67. And it also happens to one of my colleagues.

[jsilvermist]

It's working fine for me too, seems almost like you have something blocking it at an app level.

Do you and your colleagues all use a certain antivirus, firewall, etc?

[felixzapata]

We have the same laptop and no antiviruses, firewall. My colleague has Polymer cli version 1.6.x with Chrome 66 and I have Chrome 67 with Polymer cli version 1.7.x (and Node version 8). I had Polymer cli version 1.6.x but I updated it in order to mix this problem.

Under Firefox the tests are fine but with Chrome we can't debug in the browser. We had no problems with Chrome until the last two versions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen!