Combining snapshot testing and component library -- ReactiveConf 2017 talk proposal

lightning_talk_proposal.md

This is a proposal for a lightning talk at Reactive Conf. Please 🌟 this gist to push the proposal!

Combining snapshot testing and component library

Do you test presentational logic of your components? No? Yes, but you feel like you are writing a lot of dummy tests? You even probably use snapshot tests for that, but don't feel like you make enought value from them..

If so, click 🌟 button on that Gist!

I'll talk how our team is using snapshot testing to iterate faster, avoid writing dummy tests for presentational logic and building component library at the same time using our custom tool called Testshot.

We believe that testing presentational logic of your components via snapshot testing while having their real representation in front of you fits nicely with interactional tests, unit tests and business tests you already have. In case you don't have any tests yet snapshot tests are still better than nothing :)

You will also learn how such approach can be beneficial during the development of your project and what tools are available today and their pros and cons. I'll talk about React libraries, but use case should be very similar to any component based JS library out there.

🌟 this gist if you are interested, ping me on twitter(@edtsech) if you have any questions or if you'd like to meet on ReactiveConf 2017 and have a chat.

Already using Storybook for basic jest snapshot comparison and there are many useful plugins.
I think the Testshot functionality could be quite easily implemented as Storybook plugin to make it more mainstream.
I dont like reinventing the wheel.
Good work anyway and good luck.

@ShockiTV sure! Storybook has a very large ecosystem nowadays. In any case, lighting talk is not about tools, but about the approach in general. And I'm glad you are already using it!

@ShockiTV I have a couple of questions regarding Storybook and snapshot testing, if you have some time to answer them ping me on twitter(@edtsech) or write me an email (you can find it on GitHub).