Running it headless is problematic. PhantomJS uses a pretty old build of (Qt) WebKit, which - last time I checked - our polyfills don't support. SlimerJS might fare better (though it's not completely headless yet)
For testing Polymer components, your best bet is to stick to real browsers for now On Thu, Nov 20, 2014, 09:26 Ian MacLeod <[email protected]> wrote: > Yup! The --browser flag (or -b) allows you to specify a particular > browser. For example: > > wct -b Firefox > > Also, to get a list of available browsers: wct --help > > > On Wed, Nov 19, 2014, 03:00 Krunal Patel <[email protected]> wrote: > >> We here @Thoughtworks are using polymer for builfing a large complex >> application. I was looking into ways to test stuff in Polymer and came >> across Web Component Tester and a post by Addy. >> >> While running wct the tests automatically runs in all the default >> browsers installed locally. Is there a way to run the test only on one >> browser or may be run it headless. >> >> Or any other suggestions regarding testing in polymer. >> >> Follow Polymer on Google+: plus.google.com/107187849809354688692 >> --- >> You received this message because you are subscribed to the Google Groups >> "Polymer" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/polymer-dev/161d5706-6ba9-4bed-b470-494434915d80%40googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAKc-BFhcw4es-G9dTOVtf9N8VXftPkeczfrNYepdQHG5nVYpsA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
