component testing is a novel approach for testing UI components in isolation.
currently the tooling available in backstage for running tests on components in isolation is Jest.
Jest misses the crucial capability to view the component in the browser and debug it with developer tools.
We propose to use storybook to run the components in isolation and playwright for testing the components on the browser.
In addition we propose to isolate the locators that access the widgets of the UI to a separate pacakge that will be reused by the QE. Since the UI tests will be developed with the same technology as the UX - this can be achieved.
The QE will get the locators together with the deployment, and that would reduce the ping pong between qe and developers when the UI changes.