Integration testing with Testing Library in Remix - Mini Project: Build & Apply

Integration testing with Testing Library in Remix

📖 Scenario: You are building a simple Remix app that shows a list of tasks and allows users to add new tasks. You want to write an integration test to check that the tasks render correctly and that adding a new task updates the list.

🎯 Goal: Write an integration test using Testing Library that renders the TaskList component, verifies the initial tasks are shown, simulates adding a new task, and confirms the new task appears in the list.

📋 What You'll Learn

Create a mock list of tasks as initial data

Set up a test render with Testing Library's render function

Use Testing Library queries to check tasks in the document

Simulate user input and button click to add a new task

Verify the new task is displayed after adding

💡 Why This Matters

🌍 Real World

Integration tests help ensure that different parts of your Remix app work together correctly, catching bugs before users see them.

💼 Career

Writing integration tests is a key skill for frontend developers to maintain reliable and user-friendly web applications.

1

DATA SETUP: Create initial tasks array

Create a constant array called initialTasks with these exact string values: 'Buy groceries', 'Walk the dog', and 'Read a book'.

Remix

# Your code here

Hint

Use const initialTasks = ['Buy groceries', 'Walk the dog', 'Read a book'];

2

CONFIGURATION: Import render and userEvent from Testing Library

Add these import statements exactly: import { render, screen } from '@testing-library/react'; and import userEvent from '@testing-library/user-event';.

Remix

const initialTasks = ['Buy groceries', 'Walk the dog', 'Read a book'];

// Your code here

Hint

Use import { render, screen } from '@testing-library/react'; and import userEvent from '@testing-library/user-event';

3

CORE LOGIC: Render TaskList and check initial tasks

Write a test function called test('renders initial tasks and adds a new task', async () => { ... }). Inside it, render the TaskList component with initialTasks as a prop. Then use screen.getByText to check that 'Buy groceries' is in the document.

Remix

import { render, screen } from '@testing-library/react';
import userEvent from '@testing-library/user-event';

const initialTasks = ['Buy groceries', 'Walk the dog', 'Read a book'];

// Your code here

Hint

Use render(<TaskList tasks={initialTasks} />); and expect(screen.getByText('Buy groceries')).toBeInTheDocument();

4

COMPLETION: Simulate adding a new task and verify it appears

Inside the same test function, use userEvent.type to type 'Clean the house' into the input with placeholder 'New task'. Then use userEvent.click on the button with text 'Add'. Finally, check that 'Clean the house' is now in the document using screen.getByText.

Remix

import { render, screen } from '@testing-library/react';
import userEvent from '@testing-library/user-event';

const initialTasks = ['Buy groceries', 'Walk the dog', 'Read a book'];

test('renders initial tasks and adds a new task', async () => {
  render();
  expect(screen.getByText('Buy groceries')).toBeInTheDocument();
  // Your code here
});

Hint

Use await userEvent.type(screen.getByPlaceholderText('New task'), 'Clean the house'); and await userEvent.click(screen.getByText('Add')); then check with expect(screen.getByText('Clean the house')).toBeInTheDocument();

Practice

1. What is the main purpose of integration testing in a Remix app using Testing Library?

easy

A. To check how different parts of the app work together

B. To test only individual functions without UI

C. To measure app performance under load

D. To check the app's deployment settings

Solution

1. Step 1: Understand integration testing goal

   Integration testing focuses on how multiple parts of an app interact, not isolated units.

2. Step 2: Match Testing Library use

   Testing Library simulates user actions and checks UI behavior, which fits integration testing.

3. Final Answer:

   To check how different parts of the app work together -> Option A

4. Quick Check:

   Integration testing = check parts working together [OK]

Hint: Integration tests check combined parts, not single functions [OK]

Common Mistakes:

• Confusing integration with unit testing
• Thinking integration tests check performance
• Assuming integration tests check deployment

2. Which of the following is the correct way to render a Remix component with routing context for integration testing?

easy

A. render()

B. render()

C. render()

D. render()

Solution

1. Step 1: Identify routing context for tests

   MemoryRouter is used in tests to simulate routing without a real browser environment.

2. Step 2: Check other options

   BrowserRouter requires a real browser, RouterProvider is Remix-specific but not typical for Testing Library integration tests.

3. Final Answer:

   render(<MemoryRouter><MyComponent /></MemoryRouter>) -> Option C

4. Quick Check:

   Use MemoryRouter for routing in tests [OK]

Hint: Use MemoryRouter to simulate routes in tests [OK]

Common Mistakes:

• Using BrowserRouter which needs a real browser
• Not wrapping component in any router
• Confusing RouterProvider with test router

3. Given this test code snippet, what will be the output when the test runs?

import { render, screen } from '@testing-library/react';
import { MemoryRouter } from 'react-router-dom';
import UserProfile from '~/components/UserProfile';

test('shows user name after loading', () => {
  render();
  const nameElement = screen.getByText(/loading/i);
  expect(nameElement).toBeInTheDocument();
});

medium

A. Test passes because 'loading' text is found

B. Test fails because 'loading' text is not found

C. Test throws a syntax error

D. Test fails due to missing MemoryRouter

Solution

1. Step 1: Analyze render and query

   The component is rendered inside MemoryRouter, so routing context is correct. The test looks for text matching 'loading' ignoring case.

2. Step 2: Understand UserProfile behavior

   Typically, UserProfile shows 'loading' text initially before user data loads, so the text should be present immediately.

3. Final Answer:

   Test passes because 'loading' text is found -> Option A

4. Quick Check:

   Loading text present = test passes [OK]

Hint: Look for initial UI states like 'loading' in tests [OK]

Common Mistakes:

• Assuming user name appears immediately
• Forgetting to wrap in MemoryRouter
• Confusing syntax errors with runtime failures

4. You wrote this test but it fails with error: "Unable to find an element with the text: Submit".

render();
const button = screen.getByText('Submit');
button.click();

What is the likely cause and fix?

medium

A. Component not wrapped in MemoryRouter; fix by adding MemoryRouter

B. Missing user event simulation; fix by using userEvent.click(button)

C. screen.getByText is asynchronous; fix by awaiting it

D. The button text is different; fix by using correct text

Solution

1. Step 1: Check error cause

   Error says no element with text 'Submit' found, so likely the button text is different or missing.

2. Step 2: Fix by verifying button text

   Confirm the actual button text in MyForm matches 'Submit' exactly or adjust the query to match the real text.

3. Final Answer:

   The button text is different; fix by using correct text -> Option D

4. Quick Check:

   Text mismatch causes getByText failure [OK]

Hint: Check exact text in UI before using getByText [OK]

Common Mistakes:

• Assuming click() works without userEvent
• Wrapping component unnecessarily in router
• Using getByText as async without reason

5. You want to test a Remix route component that fetches data and shows a list. Which approach correctly tests the full integration including routing and data loading?

hard

A. Render the component without router and skip data mocking

B. Render the component inside MemoryRouter and mock the fetch with a test server

C. Use BrowserRouter and real API calls in the test

D. Render the component alone and call fetch manually in the test

Solution

1. Step 1: Include routing context

   MemoryRouter simulates routing in tests without needing a real browser, so wrap the component in it.

2. Step 2: Mock data fetching

   Mocking fetch with a test server or mock service avoids real network calls and controls test data.

3. Step 3: Avoid real API calls and BrowserRouter

   Real API calls slow tests and BrowserRouter requires a browser environment, not suitable for integration tests.

4. Final Answer:

   Render the component inside MemoryRouter and mock the fetch with a test server -> Option B

5. Quick Check:

   MemoryRouter + fetch mock = full integration test [OK]

Hint: Use MemoryRouter and mock fetch for full integration tests [OK]

Common Mistakes:

• Using BrowserRouter in tests
• Not mocking network requests
• Skipping router context in route tests