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.
This is Part 2 of our series, Using Jest and Testing Library with React Native. This post will cover the steps you’ll need to take to write your first test. We will also break down the code line-by-line, so you have a clear understanding of the process.
In this post, Part 1 of Using Jest and Testing Library with React Native, I’ll give a brief introduction to Jest, Testing Library, and React Native. Then, we’ll walk through how to set each of them up. This will prepare us for Part 2, creating our first test.
Expo is a platform and framework that allows you to write cross-platform code using React Native, taking advantage of the APIs native to each platform. This makes it extremely simple to develop and deploy apps to a variety of platforms. Additionally, it allows the apps to make use of the native components of whatever platform they are deployed to.
This post first reviews the different features of Expo and how they can be used to rapidly develop and deploy software. Then, we’ll talk through the steps you’ll need to take to get up and running with the tool.
It can be challenging to decide on the right strategy for reaching the mobile audience, though. If you decide an app is what you need, the next question is “what are my options?” In general terms, the types of mobile applications you could choose to build can be divided into three groups: vendor-native, cross-platform, and hybrid web.
In this post, we give an overview of the various mobile development strategies on our shortlist for enterprise clients to consider; for example, Xamarin, Flutter, React Native, and Ionic. For each tool, we give a brief introduction and highlight the key advantages and disadvantages found in implementing each mobile development approach.
- Page 1 of 2