@wejendorp@sunesimonsen Yes of cause. I don't have my computer with me. Should be MIT #license" target="_blank" rel="nofollow noopener">github.com/sunesimonsen/m… I'll add it to package.json when I'm at a computer.
@thejameskyle@_munter_@ava__js I agree with that. I usually make custom assertions for complex things that is repeated, but that is a very different workflow and I understand the wish for keeping things low level.
@thejameskyle@_munter_@ava__js Thanks for the answer. I agree power assert is pretty awesome. It of course has its limitations to how detailed and custom the error output can get. But it is definitely a winner if you want to stay with simple assertions. I tend to mostly use unexpected.js.org/assertions/any… in my tests.
If you're trying out enzyme 3 with React 16, try out unexpected-react 5 - simpler tests and much improved output! @bruderstein/enzyme-vs-unexpected-react-ee9cb099d12b" target="_blank" rel="nofollow noopener">medium.com/@bruderstein/e…