Test File Syntax Error
Error message
SyntaxError: Unexpected token in test file
Quick summary
The test file contains a syntax error — a typo, missing bracket, or unsupported syntax. Jest can't parse and run the file.
Why this happens
Missing or mismatched brackets, parentheses, or braces.
Using JSX/TypeScript syntax without the proper Jest transformer.
A trailing comma or missing comma in an array/object.
Invalid JavaScript syntax (e.g., missing semicolons in certain contexts).
Minimal example
test('bad syntax' () => { // missing comma after string
expect(1).toBe(1);
}test('bad syntax', () => { // comma added
expect(1).toBe(1);
});Fix the syntax error — in this case, add the missing comma after the test name.
How to diagnose
Read the error message — it shows the file and line number of the syntax error.
Check the indicated line for missing brackets, commas, or typos.
If using JSX/TS, verify the Jest transformer is configured (babel-jest, ts-jest).
Run npx tsc --noEmit (for TypeScript) to find type/syntax errors.
How to fix
Fix the syntax error on the indicated line.
Configure the proper Jest transformer for JSX/TypeScript.
Use an IDE with syntax checking to catch errors early.
For TypeScript: ensure ts-jest or @swc/jest is configured in jest.config.js.
How to prevent
Use an IDE with real-time syntax checking (VS Code with ESLint/TypeScript).
Run the linter before committing: npm run lint.
Configure Jest transformers for JSX/TypeScript from the start.
Related Resources
Related Lessons
- Jest Basics
Getting started with Jest.