Testing CRUD Operations with Jest and Fetch API

Welcome to another step in our journey to mastering automated API testing with JavaScript. So far, you've learned how to organize tests using Jest and the Fetch API for HTTP requests. Today, we will focus on automating tests for CRUD operations — Create, Read, Update, and Delete — which are integral actions for managing data in any application that uses RESTful APIs. Automated testing of these operations is essential to ensure that APIs function correctly and modify resources as expected. Thorough testing of CRUD operations will help you catch issues early and ensure API reliability.

In automated testing, setup and teardown are fundamental concepts that help ensure each test has a clean start and finish. Setup is about preparing what you need before a test runs, like creating test data or setting up configurations. Teardown involves cleaning up afterward, removing any leftovers from the test, such as deleting test data, so future tests aren't affected. This process makes sure tests don't interfere with each other and helps maintain data integrity and consistency across tests.

We'll use Jest's beforeEach and afterEach functions to make setup and teardown automatic. Imagine testing a todo API with CRUD operations:

• Setup Phase: Runs before every test to create a fresh todo item, providing each test with the necessary starting data.
• Teardown Phase: Runs after every test to delete the todo item, ensuring no leftover data impacts subsequent tests.

These functions handle these phases automatically, before and after every test, keeping your tests independent and the environment clean.

To effectively manage setup and teardown for CRUD operations, we utilize Jest's beforeEach and afterEach functions. These functions automate the process, ensuring each test starts with the right conditions and ends without leaving any trace. This means every test begins and ends with a clean state, which is crucial to avoid any interference between tests.

Here's an example of how the setup and teardown are structured:

const fetch = require('node-fetch');

const BASE_URL = "http://localhost:8000";

let todoId;
let todoData = {
    title: "Setup Todo",
    description: "For testing CRUD operations",
    done: false
};

beforeEach(async () => {
    // Setup Actions: Prepare a new todo
    const response = await fetch(`${BASE_URL}/todos`, {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
        body: JSON.stringify(todoData)
    });
    if (response.status !== 201) {
        throw new Error("Failed to create a todo for setup");
    }
    const data = await response.json();
    todoId = data.id;
});

afterEach(async () => {
    // Teardown Actions: Clean up by deleting the todo
    if (todoId) {
        await fetch(`${BASE_URL}/todos/${todoId}`, { method: 'DELETE' });
    }
});

Within this setup, the actions occur before each test to create a todo item, ensuring the test environment has the necessary data. After each test, the teardown actions delete the created todo, maintaining a clean slate for subsequent tests. This ensures consistent, independent test runs free from interference caused by leftover data.