Re: [w3c/webcomponents] Support `>>>` combinator in static profile (#78)

The form submission issue is tracked by https://github.com/w3c/webcomponents/issues/187, which we're intending to discuss at W3C TPAC this year.

> As you continue to compose custom elements together, how else do your properly test the combined total? How do you test `<my-app>` in a final integration test in a browser?

Even in that scenario, piercing across shadow boundaries isn't really a good way to write tests. When the implementation details of each component changes, you'd be forced to update all those integration tests.

A better way to accomplish this would be relying on public APIs of each component to test, and make sure each component has a separate unit tests for public API updating its internal states correctly. If there isn't adequate API support for writing whatever tests, then you can add test/debug only API which exposes necessary states/information. We do this in WebKit's C++ code by exposing extra JS objects which lets tests expose & manipulate internal states of WebKit even though doing so in production/user environment won't be okay due to security concerns.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/78#issuecomment-335050184