Hello, Hacker News!<p>Author here. I&#x27;m super glad to share something that we have been working on during the past couple of days. A bridge that connects the chai.js assertion library and enzyme - airbnb&#x27;s library
for testing React components in isolation and in integration.<p>A little bit of background - we developed a project that was very similar to enzyme, focusing on encapsulating the differences between React&#x27;s shallow rendering and mounting into the DOM (jsdom).
However, once enzyme came out, we decided to stop investing in it and instead migrate to enzyme.<p>I&#x27;m personally a bit surprised that people don&#x27;t define many custom assertions in their projects, while IMO they should. There are a number of great benefits such as better exception messages
better diffs, DRY etc. I&#x27;m also a chai.js maintainer, and I would love to know if you have custom assertions in your project. If so - what can we improve there, and if not - how we can
make it easier for you to start utilizing this ability.<p>The assertions is just the first piece that we are open sourcing. We have an internal lib for creating factories (ala factory girl) coming out next and more that we&#x27;ll be trying to get out in
the next couple of months.<p>So please hare your experience with testing your frontend. What are you using? What are the biggest issues you are facing? What do you want to see improved?