Any plans to address integration testing between these components? about micro-frontends

[ChristianUlbrich]

Why would integrations tests have to be any different for micro-frontends? Micro-Frontends are an architectural style to build big apps. If you want to test functionality across function verticals, you employ exactly the same methods that you'd emloyed to test yarr big olde' monolithic app. But using a composition-based approach, you can:

• version your components and hopefully rely on them sticking to SemVer and thus prevent breaking things by using meaningful versions (as you suggest); one feasible, but very specific approach for this is Canopy's Sofe
• test your components in an isolated way

If you understand components not as a mere "buy button" but an app feature (in contrast to a product feature) that are developed in real verticals (meaning they are aligned with the backend) - you can considerably narrow down the test effort. As @naltatis says, you'd want to do most of your tests at the component level and only do few high-level integration tests. Of course with a micro-frontend architecture you could test the integration of different components isolated from the real app in a small testbed application to make sure, that this combination will work in your real app.

[naltatis]

This is indeed a tricky topic.

Features inside one vertical are tested by the team itself. This is where we write most of our tests.

To make sure all pieces work together we also had projects where we've implenented an additional higher level integration test that tests a complete customer journey (eg. from homepage through checkout). For this to work the team responsible for this test must have a reliable way of identifying the relevant parts on the page (buy button, success messages, ...). The requires some coordination.

Another alternative is, that each team directly tests its direct integration points with the other teams.

I've added integration testing to my writing todo list.