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.
If youโve been writing code for a significant amount of time, youโre sure to have seen theโanything but godlyโโGod Method.โ It’s a method that performs way too many processes in the system and has grown beyond all realistic logic to become โThe Method That Does Everything.โ
This single unsightly method can span dozens, if not hundreds, of lines. Sometimes even over 1,000! This type of โugly codeโ is an unbearable beast to maintain. This is why itโs considered a โcode smellโ or anti-pattern.
In this tutorial, we walk through a tangible โGod Methodโ and step through the process to refactor it into something more manageable and human-readable. Our code is written in JavaScript for a Node.js service, but the principles apply to any language.
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.
This is a tutorial for how to use the VS Code Remote-Containers extension to containerize your development environment.ย First, I will discuss my reasons for separating my programming environment and why virtual machines didnโt work.ย Then, Iโll show a simple example using a containerized Python development environment.ย Finally, Iโll give you my reasons why containerizing the development environment fits what Iโm looking for in a solution.