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.
Push notifications are a vital feature for todayโs enterprise mobile applications. Why are they so important? They allow the business to communicate with its users without requiring the application to be in an open state.
Xamarin.Forms allows developers to create user interfaces in XAML with code behind it in C#, which then renders as native controls on iOS and Android platforms.
In this blog, we go through a step-by-step tutorial for setting up and configuring push notifications on Xamarin.Forms applications using Azure Notification Hubs. Let’s dive right in.