Unit testing loaders and actions in Remix - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What does this loader return?

Given this Remix loader function, what will be the JSON response when called?

Remix

import { json } from '@remix-run/node';

export async function loader() {
  return json({ message: 'Hello from loader', count: 3 });
}

A {"message":"Hello from loader","count":3}

B {"msg":"Hello from loader","count":3}

C {"message":"Hello from loader","count":"3"}

D {"message":"Hello from loader"}

💡 Hint

Look carefully at the keys and value types in the returned JSON.

The loader returns a JSON response with keys exactly as defined: 'message' and 'count' with count as a number 3.

❓ state_output

intermediate

What is the action's returned status code?

Consider this Remix action function. What HTTP status code will the response have?

Remix

import { json } from '@remix-run/node';

export async function action({ request }) {
  const formData = await request.formData();
  const name = formData.get('name');
  if (!name) {
    return json({ error: 'Name required' }, { status: 400 });
  }
  return json({ success: true });
}

A 200

B 400

C 500

D 404

💡 Hint

Check the condition for returning status 400 carefully.

If 'name' is missing, status 400 is returned. Otherwise, the default status 200 is used.

🔧 Debug

advanced

Why does this loader test fail?

This test for a Remix loader fails. What is the cause?

Remix

import { loader } from './route';

test('loader returns correct message', async () => {
  const response = await loader();
  const data = await response.json();
  expect(data.message).toBe('Hello from loader');
});

A response.json() is not a function on the returned object

B loader() is missing await keyword

C The test expects wrong message string

D loader() returns a Response object, but test treats it as plain object

💡 Hint

Think about what loader() returns and how to extract JSON from it.

Remix loaders return a Response object. To get JSON, you must call response.json() which returns a promise.

📝 Syntax

advanced

Which action code snippet correctly handles form data?

Select the code snippet that correctly extracts 'email' from form data in a Remix action.

A const email = request.formData().get('email');

B const email = await request.getFormData('email');

C const formData = await request.formData(); const email = formData.get('email');

D const formData = request.formData(); const email = formData.email;

💡 Hint

Remember that formData() returns a promise and you must await it.

request.formData() returns a promise, so you must await it before calling get(). Option C does this correctly.

🧠 Conceptual

expert

What is the best way to unit test a Remix loader that depends on session data?

You have a Remix loader that reads user info from a session cookie. Which approach correctly isolates the loader for unit testing?

A Call the loader with a real request object and real session cookie from a test browser

B Mock the session retrieval function and pass a fake request with cookie header to the loader

C Skip testing the loader and only test the UI components that use its data

D Modify the loader to not use session and instead pass user info as a parameter

💡 Hint

Think about how to isolate external dependencies in unit tests.

Unit tests should isolate external dependencies. Mocking session retrieval and passing a fake request allows testing loader logic without real sessions.

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