Tools: Post 6.0.0 Design

[justinfagnani]

We would like to design a more modern, flexible, and hopefully smaller web-component-tester after we take care of supporting the Polymer 2.0 release.

Some potential goals of this could include:

• Separation of concerns between test discovery and launching, browser launching, and test libraries.
• Reuse standard ecosystem testing infrastructure as much as possible
• Reduce the download size of the library
• Support multiple, or completely bring-your-own, client-side testing libraries. Don't require Mocha.
• Speed up tests by keeping browsers open between tests.
• Allow multiple projects with different test runner dependencies to be tested together, like Tattoo but without as tight of a coupling to WCT
• Allow combination client/server tests to be written.
• Support headless Chrome

[Hotell]

webpack interop would be neat as well ;)

[stale[bot]]

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.