In our last tutorial, we went over style testing. In this tutorial, we will go over functional testing for your React Native app.
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.
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.
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.
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.