tag:blogger.com,1999:blog-581197352358126527.post2436705575493450542..comments2024-03-28T00:32:25.959-07:00Comments on japh(r) by Chris Strom: Upgrading a Polymer Element to Polymer 0.8Anonymoushttp://www.blogger.com/profile/00135361916531185929noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-581197352358126527.post-41995137764777954192015-04-09T09:21:02.265-07:002015-04-09T09:21:02.265-07:00That's super helpful. I'm going to give th...That's super helpful. I'm going to give that a try in a few days. Your explanation feels right based on what I was seeing. If so, this seems like something that ought to be baked into WCT.<br /><br />Thanks!Anonymoushttps://www.blogger.com/profile/00135361916531185929noreply@blogger.comtag:blogger.com,1999:blog-581197352358126527.post-79858708162894847962015-04-08T21:21:22.440-07:002015-04-08T21:21:22.440-07:00We ran into the issue of console errors not showin...We ran into the issue of console errors not showing up in WCT and not causing any sort of failure either. We ended up writing a quick script that we load right after browser.js and polymer in every test HTML file. The script registers window.onerror handler that has a test("has no console errors", ...) and then assert.fail it with the error message. This causes our test suite to fail when a console error occurs before the rest of the suite starts running.<br /><br />This might be what's happening with your missing test. The script errors out before the test runner even begins running the test. We had the same problem and found 10 tests that weren't even running.<br /><br />Hope this helps!Jim Simonhttps://www.blogger.com/profile/00575168142570579191noreply@blogger.com