Unit testing loaders and actions in Remix - Mini Project: Build & Apply

Unit Testing Loaders and Actions in Remix

📖 Scenario: You are building a simple Remix app that manages a list of books. You want to ensure your data loading and form submission logic works correctly by writing unit tests for your loader and action functions.

🎯 Goal: Write unit tests for a Remix loader that fetches book data and an action that adds a new book. You will create test data, configure test helpers, write the core test logic, and complete the test setup.

📋 What You'll Learn

Create a test data array called books with two book objects

Add a configuration variable newBook representing a book to add

Write a test for the loader function that returns the books array

Write a test for the action function that adds newBook to books

💡 Why This Matters

🌍 Real World

Unit testing loaders and actions helps catch bugs early in Remix apps that fetch or modify data, improving app reliability.

💼 Career

Knowing how to write unit tests for Remix loaders and actions is valuable for frontend developers working with Remix to ensure code quality and maintainability.

1

Create test data array books

Create an array called books with two objects: { id: 1, title: '1984' } and { id: 2, title: 'Brave New World' }.

Remix

// Create the books array with two book objects
// Your code here

Hint

Use const books = [ ... ] with two objects inside.

2

Add configuration variable newBook

Add a constant called newBook with the object { id: 3, title: 'Fahrenheit 451' }.

Remix

const books = [
  { id: 1, title: '1984' },
  { id: 2, title: 'Brave New World' }
];

// Add newBook object here
// Your code here

Hint

Define newBook as a constant with the given object.

3

Write test for loader function

Write a test function called testLoader that returns the books array.

Remix

const books = [
  { id: 1, title: '1984' },
  { id: 2, title: 'Brave New World' }
];

const newBook = { id: 3, title: 'Fahrenheit 451' };

// Write testLoader function here
// Your code here

Hint

Create a function named testLoader that returns the books array.

4

Write test for action function

Write a function called testAction that adds newBook to the books array and returns the updated array.

Remix

const books = [
  { id: 1, title: '1984' },
  { id: 2, title: 'Brave New World' }
];

const newBook = { id: 3, title: 'Fahrenheit 451' };

function testLoader() {
  return books;
}

// Write testAction function here
// Your code here

Hint

Create a function named testAction that adds newBook to books and returns the updated array.

Practice

1. What is the main purpose of unit testing loaders and actions in Remix?

easy

A. To check CSS styles are applied properly

B. To test the UI rendering of components

C. To verify data fetching and form handling logic works correctly

D. To measure page load speed

Solution

1. Step 1: Understand loader and action roles

   Loaders fetch data and actions handle form submissions in Remix.

2. Step 2: Identify unit testing focus

   Unit tests for loaders and actions check their logic, not UI or styles.

3. Final Answer:

   To verify data fetching and form handling logic works correctly -> Option C

4. Quick Check:

   Unit testing loaders/actions = verify logic [OK]

Hint: Loaders/actions test logic, not UI or styles [OK]

Common Mistakes:

• Confusing UI rendering tests with loader/action tests
• Thinking unit tests check CSS or performance
• Ignoring form handling in action tests

2. Which of the following is the correct way to create a mock Request object for testing an action in Remix?

easy

A. new Request('/path', { method: 'POST', body: new URLSearchParams({ key: 'value' }) })

B. new Request('/path', { method: 'GET', headers: { 'Content-Type': 'application/json' } })

C. new Request('/path', { method: 'DELETE' })

D. new Request('/path', { body: JSON.stringify({ key: 'value' }) })

Solution

1. Step 1: Identify action request method

   Actions usually handle POST requests with form data in body.

2. Step 2: Check correct Request creation

   new Request('/path', { method: 'POST', body: new URLSearchParams({ key: 'value' }) }) uses POST method and URLSearchParams body, matching form submission.

3. Final Answer:

   new Request('/path', { method: 'POST', body: new URLSearchParams({ key: 'value' }) }) -> Option A

4. Quick Check:

   Mock POST with URLSearchParams body = new Request('/path', { method: 'POST', body: new URLSearchParams({ key: 'value' }) }) [OK]

Hint: Use POST and URLSearchParams for form data in mock Request [OK]

Common Mistakes:

• Using GET method for action tests
• Passing JSON string body without proper headers
• Omitting method in Request constructor

3. Given this loader test snippet, what will result contain after calling await loader({ request }) if the loader returns json({ message: 'Hello' })?

const request = new Request('http://localhost');
const result = await loader({ request });

medium

A. A Response object with JSON body

B. { message: 'Hello' }

C. undefined

D. An error thrown

Solution

1. Step 1: Understand Remix loader return

   Loaders return Response objects, often created by json() helper.

2. Step 2: Analyze test result type

   Calling loader returns a Response, not plain object.

3. Final Answer:

   A Response object with JSON body -> Option A

4. Quick Check:

   Loader returns Response, not plain object [OK]

Hint: Loaders return Response objects, not raw data [OK]

Common Mistakes:

• Expecting plain object instead of Response
• Not awaiting async loader call
• Confusing loader with action return types

4. You wrote a test for an action but it always fails with TypeError: request.formData is not a function. What is the most likely cause?

medium

A. The URL in the Request is invalid

B. The action is missing a return statement

C. The test is calling loader instead of action

D. The mock Request object does not have a formData method

Solution

1. Step 1: Understand error meaning

   TypeError means formData method is missing on Request object.

2. Step 2: Identify mock Request issue

   Node's Request may lack formData; test must mock or polyfill it.

3. Final Answer:

   The mock Request object does not have a formData method -> Option D

4. Quick Check:

   Missing formData method causes TypeError [OK]

Hint: Mock formData method on Request to fix TypeError [OK]

Common Mistakes:

• Assuming action code is wrong instead of test setup
• Ignoring need to mock formData in tests
• Confusing loader and action calls in tests

5. You want to unit test an action that handles a form with optional fields. Which approach ensures your test covers both filled and empty optional fields correctly?

hard

A. Skip testing optional fields since they are not required

B. Write separate tests with mock Requests: one with all fields, one missing optional fields

C. Use a single test with empty strings for all optional fields

D. Test only with all fields filled, assuming empty fields behave the same

Solution

1. Step 1: Understand optional field behavior

   Optional fields can be present or absent, affecting action logic.

2. Step 2: Design tests for coverage

   Separate tests with and without optional fields ensure full coverage.

3. Final Answer:

   Write separate tests with mock Requests: one with all fields, one missing optional fields -> Option B

4. Quick Check:

   Separate tests for optional fields = full coverage [OK]

Hint: Test both presence and absence of optional fields separately [OK]

Common Mistakes:

• Assuming one test covers all optional cases
• Ignoring empty or missing optional fields in tests
• Skipping optional fields testing entirely