Actually, now that I've actually tried this for a few days, I've learned that what I really want is probably something like:
1. Run the unit tests on the uncompiled code (so that stack traces and the debugger are actually useful)
2. BUT display the errors from compiling the unit test (to display type errors, which are useful)
I'd love to hear what other people's workflows are like using Plovr/closure compiler and tests.
On Oct 22, 2013, at 22:09 , Greg Perkins <gper...@gmail.com
> You're not the only person! I definitely want that too. In past projects I've ended up with just about your proposed configuration, except using source_test.soy files instead of source_test.html and plovr's soyweb to serve them. No scripting unfortunately. :-(
> I think something that automates this boilerplate would be quite useful!
> You received this message because you are subscribed to the Google Groups "plovr" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to plovr+un...@googlegroups.com
> For more options, visit https://groups.google.com/groups/opt_out