Our team does a lot of our UI development in Storybook. If you are curious about how we manage our business logic, you can read more about how we build our UI components here.
Storybook has been working hard to improve its UI testing features and introduced integrated interactive testing in version 7, where you can build UI tests that can run in your preferred test runner. We decided to try this with our components, and this blog will go into what we have found so far with our experimentation.
As you've read in our previous Summer Health Dev Blog post, Summer Health is an early-stage start-up whose goal is to simplify healthcare and provide better access to doctors for patients. When we first started building our applications last summer our main focus was to move quickly while building a base for the future. At first, tailwind seemed like the right choice. If offered us a simple CSS utility interface to build out pages quickly and easily. In addition, there are several sites with well-documented tailwind recipes we were able to lean on. However, as time passed, we started to encounter issues with relying upon tailwind alone.