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.
Client: A large federal government agency Industry: Federal Government Services: DevSecOps Platform Engineering, CI/CD Architecture, Cloud Migration, Application Security Integration Outcome: A unified CI/CD platform supporting 400 to 500 applications across four technology stacks, with time-to-deployment reduced by more than 30% and thousands of engineering hours saved annually. Large federal agencies rarely run one technology stack. Java teams, JavaScript and …
Client: A nonprofit organization specializing in audio and video Bible translation and distribution Industry: Non-Profit and Media Content Technology Services: Custom Software Development, Mobile App Development, Cloud Migration, Legacy Application Modernization, Software Architecture Outcome: A multi-year platform partnership that took the organization from a single cross-platform mobile app to a full content platform, including a serverless media pipeline that reduced …