Jest · question
Question 4 of 49
How do you structure a typical Jest test file?
← All Jest questions
Re-explain
A well-structured Jest test file typically follows this pattern:
// Import dependencies
import { functionToTest } from '../src/utils';
// Describe the module/component being tested
describe('functionToTest', () => {
// Group related tests
describe('when given valid input', () => {
test('should return expected result', () => {
// Arrange
const input = 'test';
// Act
const result = functionToTest(input);
// Assert
expect(result).toBe('expected');
});
});
describe('when given invalid input', () => {
test('should throw an error', () => {
expect(() => functionToTest(null)).toThrow();
});
});
});
Rewriting in plainer words…
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
Why there's no diagram: “”
The diagram below the answer is the concept .
Jump to it ↓
What should the new diagram focus on?
How well did you know this?
AI:
Saved in this browser - sign in to keep your review list.
How should your speech become text?
Listening… your words appear above as you speak - tap Stop when you're done.
Recording · cr - tap Stop & transcribe when you're done.
Transcribing with AI…
Voice:
Keep going - a few more words and AI can grade it.
Interview lens
Likely follow-ups, what you can say, and the weak answers to avoid.
Pro · $10/mo
42 of 49 Jest answers are in Pro.
Full answers, code samples, and AI explanations that go simpler or deeper. Cancel anytime.
-
Full answers + code
-
AI explanations, simpler or deeper
-
1,000 AI credits / month
-
Cancel anytime