Hi, We've been adding a bunch of polymer elements to our code (kudos btw, polymer rocks!), and have been following the same pattern for testing as the polymer elements themselves.
One problem with this approach is that since the tests run inside an iframe (when run from the commandline), it is hard to debug any errors. We've extended our local copy of htmlTest.js and mocha-htmlTest.js a bit to improve this by a- allowing the test inside the iframe to use mocha (with a special reporter that postMessages results to the parent frame) b- serialising Error objects such that callstacks are preserved when sent to the parent frame c- posting console.log messages to the parent frame But even with these changes, it's not always straight forward to spot what is going wrong. On top of that, our "hacks" are somewhat bolted on to the side, rather than something that is very extensible. Do you (or perhaps the karma team) have any plans for improvements here? Or should we continue to tweak the existing parent vs iframe communication a bit more to help with developing/debugging elements? /Cheers, Jelte Jelte Liebrand | Software Engineer | [email protected] <[email protected]> | +1 (415) 318 6507 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/CAOOg8mr-KDB0SoMu2XJZxRKaZTiEaSmuPnDKfV6rpDngZYPD0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
