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.
Infrastructure as Code (or IaC) is the process of using code and versioning in the same way you do your source code to manage your networks, VMS, and Azure resources. IaC generates the same environment every time it is applied, and itโs an important DevOps practice to use alongside continuous delivery.
The release pipeline executes this model to configure target environments. If you need to make any changes, you edit the source, not the target environment. This allows you to create reliable and stable environments on-demand that can be validated, tested, and repeated.
In this blog, weโll look at how we can use Azure CLI and Azure DevOps Release Pipelines to make this happen. Iโll walk you through all the steps you need to take to get set up.