solid-testing-library VS my-job-tracker

A team and I built an NPM package that can be installed into any SolidJS application to help visualize your signals and how they communicate. I wanted to test if the components would render during the development stage. I found Solid’s testing library and proceeded to follow the steps.

With regards to third-party libraries, Solid does not have a lot yet, but it does have first-party libraries. Its first-party libraries are the equivalent of other popular libraries in other JavaScript libraries, such as Solid App Router for routing, Solid Testing Library for writing component tests, and Solid Transition Group for animations.

Well, you certainly could do that, but not even I'm suggesting you should, because components are usually used in a DOM context and not solely in a component context, as rendering could introduce side effects. Instead, I want to point you at Solid's testing library.

Solid Jest Solid Testing Library Storybook Example

After applying each step I realized that I was adding more dev dependencies and config files than I intended. The folder structure seemed convoluted especially because the product was an NPM package and didn’t have the file path of a full-stack application. Each component depended on the other and so I couldn’t evaluate an individual component. Which led to the biggest obstacle, importing and rendering components. I started searching for alternative solutions and I recall using Cypress in a different project I worked on.