Hi all. We’ve been building UI extensions for a couple of years and have never managed to find or elicit any documentation (or even basic guidance) on how Shopify expects developers to test their UI extension components. While we may be writing JSX and feel like we’re in the comfortable familiarity of React-land, once it comes to testing the components we’re writing for UI extensions it quickly becomes clear that this is not the case. There is a @remote-dom/testing package (ref) which has some very minimal documentation in its README, but nothing that demonstrates how developers can leverage it to render their components for testing. There were one or two community-supplied examples elsewhere which I’ve since been unable to find, but I recall that neither of them were particularly “clean”.
Shopify’s adoption of an “exotic” rendering approach for UI extensions – which they themselves created and maintained – without supplying information as to how developers are expected to automate tests for the things they’re building on top of it, results in a lack of quality control and increased developer pain.
Would someone on Shopify’s side who’s involved in the UI extension/remote-dom side of things be able to share examples of how Shopify expects developers to be testing their components, from test setup to teardown? Thanks! 
