This series covers testing React Native apps with Jest and Testing Library. In our past tutorial, we went over testing text and a button. In this tutorial, we will go over Testing Styles in your React Native app.
Using Jest and Testing Library with React Native Part IV: Testing a Button
In our last tutorial, we went over how to test for an element/component that is not found. In this tutorial, we will go over adding a button to our React Native codebase. After the button is added, we’ll test it.
Documenting with Markdown
In today’s environment, we have an embarrassment of riches when it comes to documenting our applications. We have a multitude of word processors, websites with word processors built in, wikis, and notes applications galore.
So you may be wondering, is there even any point in talking about ways to document your application? I think there is. In this blog, Iโll share my documentation tool and how and why you can use it in your own projects. Itโs called Markdown.
Cook Your Own Modal with Styled Components
I created several JavaScript modal dialogs – I always extend a framework modal instead of scratch-coding my own. I thought I knew the things a framework needs to implement in order to present a modal but did I? There was only one way to find out: cook my own JS browser modal, and that is exactly what weโll do in this post.
In this blog, I’ll cover a short approach to hand-coding your own modal with Styled Components. You can find the entire project on GitHub.
Using Jest and Testing Library with React Native Part III: Element Not Found
In the last installment (Part II), we walked through creating and executing our very first test. With that out of the way, let’s move on to something slightly more complicated. Elements that cannot be found typically are elements that are initially hidden. In this post, weโll cover how to test for an element or component that isnโt found.