auto-comment[bot]
commented
5 years ago Hi there! Thank you for taking the time to submit a talk! Speakers like you make the DC tech community awesome — and we’re glad you’re here.
Rest assured that organizers of quite a few meetups have just been notified of your proposal.
Want to target one or two groups specifically? Mention the group by tagging @dctech/[group] — but please avoid tagging groups at random or tagging more than one or two. Thanks for keeping this group productive and spam-free!
Not interested in giving this talk anymore? Not a problem at all! Thanks for considering it in the first place! Go ahead and close this issue, so we know not to bother you about it.
stale[bot]
About You
Your Name:Matt Crowder
Twitter handle (optional): https://twitter.com/mcrowder65
The best way to reach out to you: email - mcrowder65@gmail.com
A quick bio: Software engineer currently at Walmart labs, passionate about react and javascript, I enjoy teaching javascript, running, and lifting weights.
Your Talk
Title: react-testing-library What your talk is about: If you had to rewrite your tests when writing a hook in your React application, then you're writing tests wrong.
react-testing-library is what it sounds like, but more importantly, it encourages writing tests in the way that your end users will be using your components.
In this talk, I will first introduce react-testing-library, what it is, what it encourages, and what it does best. I'll then dive into how to effectively test a react component, first a smaller component, then a "larger" component with redux, i18n dependencies, etc., then I will show all of the different APIs that react-testing-library provides, and how to effectively use them. Then, I'll show how to write effective tests across an entire application (writing reusable, effective tests that are not brittle). How long will your talk be?
Meta
Do you need help crafting your talk?