testing

Modules are super useful for splitting our projects into smaller, more manageable parts. But they could be doing more. Here, we look at how a utility module can ease the burden not only for production targets but also for test targets.

Core Data and Unit Testing haven't always been the best of friends ⚔️. Core Data is all about persisting. Unit testing is all about forgetting. Here, we look at how they can work together with the help of UIKit to ensure that we gain the confidence we need to ship an app.

An uncomfortable truth is that praising firefighting developers might just be leading to more fires. Here, we look at why needing firefighting developers is a sign that your processes need to be improved, as avoiding fires is better than managing fires.

We want to test that our network stacks can make network requests as intended but without actually making those requests. Here, we look at how to split our networking stack into components to allow easy unit testing.

No one said running your unit tests on Travis CI would be easy. Who knew running tests via the Xcode UI wasn't the same as running those tests via the terminal 🤷‍♂️? Here, we look at how to prepare your test targets for running on Travis CI.

When extracting functionality, we are often trading local complexity for communication complexity. A useful mental framework for knowing if that exraction is worthwhile is Single Responsibility Principle (SRP). Here, we look at how to extract functionality from a view controller using SRP.

Dependency injection is one of the superpowers that developers can utilise to produce code that is more predictable and easier to test. Here, we look at dependency injection - what it is and how we can utilise it.

What is blackbox testing? What is whitebox testing? Here, we look at both techniques and how they can be utilised to ensure that the tests we write thoroughly test our production code.

You are a great developer, so why go through the hassle of writing unit tests? Here, we look at the reasons beyond writing unit tests and why great developers write them.

What to test? How to test? Are two questions that every developer new to unit testing faces. Here, we look at how to answer those questions by walking through the process of testing a class.

Everywhere you look, you are being told to write automated tests, but what even are automated tests? Here, we look at what testing is, why you need automated tests, who should write them and when to write them.

Oversharing is bad. Social media taught us this. But so did `101 Introduction to Object Oriented Programming`. Here, we look at how to avoid oversharing by respecting encapsulation.

Strong encapsulation is the cornerstone of good design. Here, we look at how to protect against outside change

Boundary Value Analysis and Equivalence Partitioning are essential tools in any QA's toolbox when designing testcases. Here, we look at what they are and how to use.