Writing a basic Jest unit test

What's really being asked

Whether you can structure a minimal, correct Jest test and choose the right matcher, including edge cases.

The full answer

First you import the function under test from utils.js. describe groups related test cases under a label, usually the function name, which keeps output readable. Each individual case uses it (or its alias test), which takes a descriptive name and a callback containing the actual test. Inside the callback you call the function with chosen inputs and assert the result using expect with a matcher: toBe for primitive equality, toEqual for deep object or array equality, and others like toThrow for error cases. A good unit test covers the normal case plus edge cases such as empty input or unusual characters, and each test should be independent so order does not matter. You run them with the jest command.

The mistakes people make

Forgetting to import the function, writing a test body with no expect call so nothing is actually asserted, using toBe for object comparison (which fails on reference inequality), or only testing the happy path.

What usually comes next

toBe versus toEqual, testing thrown errors, beforeEach setup, and why tests should be independent.

A concrete example

import { formatTitle } from './utils'; describe('formatTitle', () => { it('capitalizes the first letter', () => { expect(formatTitle('hello')).toBe('Hello'); }); it('handles an empty string', () => { expect(formatTitle('')).toBe(''); }); }); The describe block names the unit, each it states an expectation, and expect with toBe asserts the exact return value for both a normal and an edge input.