WCT in integration tests on travis failing

[rictic]

It looks like Polymer/polymer-cli#554 broke the integration tests (e.g. ApplicationGenerator was renamed to createApplicationGenerator). It looks like the integration tests aren't run on travis.

More broadly, while integration tests can be a pain, they're the most valuable tests to have, as the most brittle parts of a system are at the integration points, and there's no substitute for testing a system end to end. I think we'd end up saving time and effort if as many integration tests as possible ran with npm test, and I think we should definitely have all tests running on travis.

[FredKSchott]

@rictic 100% agreed, our current plan is to work on these in the next few weeks as we get tooling ready for Polymer 2.0. I have a branch to get them running on our sample projects as well, which would be more complete and flexible if we can get it merged.

FWIW these were never working completely, even when they were added, so we were never able to integrate them into our CI process. We've wanted to for a while but just haven't had the resource to prioritize.

[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.