Introduction to Pain Free Mocking with Jest

Course Introduction

Prerequisites

Importance of automated testing

Test classification using the test pyramid

The testing pyramid

What is Jest

Application setup

Everything you need to know to start testing with Jest. You'll set up your environment, learn how to think like a tester with the Testing Pyramid and you'll even write your first test!

Introduction

What is unit test

Entry and exit points

First unit test

Naming and organizing tests

Exercise 1 (Testing for Hash Password Functions)

Exercise 1 solution (Testing for Hash Password Functions)

Set up Jest extension

Introduction to Test Doubles

Mock database

How to test Express controller functions using unit testing principles

Unit test express controller

Exercise 2

Exercise 2 solution

Test coverage

Get started with unit testing and mocking. Write more unit tests, learn how, when, and why to use mocks, stubs, and spies, mock databases and participate in some fun testing exercises.

Getting started with mocking and unit testing

What is integration test

How to use a separate test database instance for testing purposes

Separate database for testing purposes

Test HTTP endpoint

Parallel tests and database connection

Database connection and parallel tests

Exercise 1 (Testing the Login Controller)

Exercise 1 solution (Testing the Login Controller)

Mock API integration using Jest

Mock API integration using Nock

Get started with integration testing. Separate the database from your tests, learn how to test HTTP endpoints, run parallel tests, mock API integrations and participate in even more fun exercises.

Getting started with integration testing

Introduction to test containers

Setup test containers

How to mock the dynamic split join pattern

How to mock slow network

How to mock network failures

Learn advanced mocking and testing techniques. Test complex edge cases like slow or inconsistent networks and learn how to create consistent testing environments with test containers.

Advanced mocking and integration testing

Test costs and maintainability

Version control checks

Create CI/CD pipeline

Note on code coverage

Agile testing quadrant

Become a test strategist by learning about test costs, maintainability and how to have a hollistic testing approach with the Agile Testing Quadrant. Add your tests to the development cycle by setting up Git hooks with Husky and CI pipelines with GitHub actions.

Testing strategy

Conclusion

You did it! By now you'll feel confident testing JavaScript applications with Jest because you have all the knowledge and tools you need to test applications in the real world without headaches.

**Pain Free Mocking with Jest** teaches you how to effectively and painlessly test JavaScript applications with Jest. You'll start by learning how to write unit and integration tests as well as the 'How', 'What', and 'When' of Mocks, Stubs, and Spies. Then we'll move to more advanced technique and strategies you'll be using for the rest of your career, including how to have a hollistic approach to testing and how to automatically add your tests in the development lifecycle.

### The Issue With Unit Testing & Mocks

Writing unit tests has always been equal parts important and confusing. 

While writing your first unit test is simple and easy, the learning curve becomes very steep very quickly once you have to test actual real-life scenarios. 

Because suddenly, you have to know how to **mock a database call** or **spy an HTTP request** or **stub a 3rd party API with a security token**. When you have to test real-life scenarios like that, things become much more complex than they initially seemed.

With every test case being different from the next one, and with Mocks not being used anywhere else in coding except for testing, it's hard to find quality information online. Every answer is different from the next one and is aimed for an ultra-specific scenario that won't necessarily apply to any other case, including yours. 

Instead of making things clear, this confuses things even further. 

### How "Pain Free Mocking with Jest" Helps:

"Pain Free Mocking with Jest" is designed to make testing painless by helping you understand once and for all the 'How', 'What', and 'When' of Mocks, Spies, and Stubs using the Jest testing framework.

You will learn how to write simple and complex test cases, utilize Jest's mocking capabilities, and gain hands-on experience with real-world testing scenarios that involve Databases, HTTP requests, and 3rd Party APIs. 

By the end of the course, you'll feel confident using Mocks, Spies and Stubs in any scenario you may need them. You'll have all the knowledge and tools you need to create complete test suites and confidently test JavaScript applications *with* mocking *without* headaches.

### Course Content Overview

Course Overview:
Total Modules: **6**
Total Lessons: **37**
Total Video Runtime: **2 hours, 28 minutes**

### Summary:
- Build and test a Node.js REST API application with authentication features like 'Sign Up' and 'Sign In'. 
- Learn how to test everything from simple functions all the way to Controllers that interract with 3rd party web services.
- Learn the 'What', 'How', and 'When' of Mocks, Spies, and Stubs.
- Learn to see your application code in testable units. 
- Write integration tests for HTTP endpoints, controllers, middleware functions, and 3rd party integrations.
- Create Git hooks to run unit tests before each commit 
- Build a CI pipeline using Github Actions to automate running integration tests on each git push to Github.

Learn to confidently test JavaScript applications and mock dependencies using Jest, the pain-free way. 

Understand how to painlessly use Mocks, Spies, and Stubs to test any part of your application, without worrying about Databases, APIs and Security Tokens. 

After finishing this course (which only takes a single afternoon), you'll feel confident in your testing skills because you'll have all the knowledge and tools you need to effectively and painlessly test even complex applications in the real world without headaches.

Pain Free Mocking with Jest

How to write unit and integration tests with Jest

How to test functions that interact with Controllers, APIs, and Databases (without relying on their responses)

How to test code in isolation with Mocks, Spies, and Stubs using Mockingoose

How to write integration tests for HTTP endpoints and database connections

Advanced mocking and integration testing techniques like the 3A pattern, network manipulation, and more

How to become a test strategist with the Agile Testing Quadrant, create CI test pipelines, and add tests to the development lifecycle

This article aims to debunk the common misconception held by many developers, especially those entering the field, who believe that achieving 100% code coverage is the ultimate goal of testing. From the perspective of an experienced software engineer and educator, this article will explain why this belief is flawed and provide a more beneficial approach to software testing.

Although the idea of complete code coverage may seem appealing, it is a misconception that it is either achievable or an accurate measure of code quality. During my time as a learning facilitator at a coding bootcamp, I frequently noticed aspiring software engineers striving for that elusive 100% coverage. However, this metric can be misleading.

// A simple function with 100% code coverage
function add(num1, num2) {
  return num1 + num2;
}

test('adds 1 + 2 to equal 3', () => {
  expect(add(1, 2)).toBe(3);
});

In the above example, the test provides 100% code coverage for the 

 function. However, it does not test the function against a variety of inputs, edge cases, or failure scenarios. Therefore, 100% code coverage does not imply that the function is 100% correct or bug-free.

---
title: Note on code coverage
privateVideoUrl: https://stream.mux.com/ZwJSoJNrcDcOJhstWu7CHkgyhe5jzv1zOi9L01nxwtIc.m3u8
isPublicLesson: false
---

# Debunking the Myth of 100% Code Coverage

## Introduction

This article aims to debunk the common misconception held by many developers, especially those entering the field, who believe that achieving 100% code coverage is the ultimate goal of testing. From the perspective of an experienced software engineer and educator, this article will explain why this belief is flawed and provide a more beneficial approach to software testing.

## The Reality of 100% Code Coverage

Although the idea of complete code coverage may seem appealing, it is a misconception that it is either achievable or an accurate measure of code quality. During my time as a learning facilitator at a coding bootcamp, I frequently noticed aspiring software engineers striving for that elusive 100% coverage. However, this metric can be misleading.

```javascript
// A simple function with 100% code coverage
function add(num1, num2) {
  return num1 + num2;
}

test('adds 1 + 2 to equal 3', () => {
  expect(add(1, 2)).toBe(3);
});
```

In the above example, the test provides 100% code coverage for the `add` function. However, it does not test the function against a variety of inputs, edge cases, or failure scenarios. Therefore, 100% code coverage does not imply that the function is 100% correct or bug-free.

## Understanding Code Coverage

Akinwale Folorunsho Habibullah

When starting out with testing, many developers set a goal of achieving 100%

What doesn't realize is that complete coverage is really attainable, nor should

When I worked as a learning facilitator at the last coding bootcamp, I usually

software engineers strive to achieve 100% code coverage. While I appreciate the

I honestly give feedback that this is not a good metric. Here's why.

Code coverage alone doesn't tell the whole story. It only represents how much

touched by tests, not how well those cases are validated. Having coverage on

doesn't guarantee the absence of bugs either, as edge cases may remain untested

grows larger, the number of possible paths through the code expands

infeasible to examine every single combination of inputs and conditional

our methods. Significant efforts will be wasted aiming for coverage that

value. Most experts recommend focusing coverage above 80% for critical parts of

The priority should be on thoroughly testing core business logic over and

it's begin the last few percentage points.