JavaScript RegExp test() Method

What You’ll Learn

test() is the fastest way to ask “does this pattern match?” It returns true or false—nothing else. Use it in validation, filtering, and guard clauses when you do not need capture groups or match text.

Introduction

After you build a regular expression, the next step is running it against text. Sometimes you need the matched substring and capture groups—that is what exec() is for. Often you only need a yes-or-no answer: Is this a valid email shape? Does the filename end in .pdf? Does the log line contain ERROR? For those cases, test() is the right tool.

RegExp.prototype.test() searches a string for the pattern and returns a boolean. It is readable in conditionals, works with every flag, and is one of the most common regex calls in real JavaScript code.

Understanding the test() Method

regex.test(string) runs the pattern held by regex against string:

• Match found — returns true. The pattern matches at least one substring of the input.
• No match — returns false. The pattern cannot match anywhere in the string.
• No match details — unlike exec(), you do not get text, groups, or index. Only the boolean.
• Global regex — with the g or y flag, test() updates regex.lastIndex for the next call.
• Coercion — non-string input is converted with ToString before matching.

How to Use test()

Call test() on a RegExp object and pass the string to check. Use the result directly in if statements, ternary expressions, or .filter() callbacks:

if (/^\d+$/.test(input)) {

  console.log("Digits only");

}



const hasError = /ERROR/i.test(logLine);

const valid = /^[\w.-]+@[\w.-]+\.\w+$/.test(email);



items.filter((item) => /\.pdf$/i.test(item));

Prefer test() when you only need a boolean. Switch to exec() or match() when you need the matched text or capture groups.

📝 Syntax

regex.test(string)

Parameters

• regex — the RegExp object with your pattern and flags.
• string — the text to search (coerced to string if needed).

Return value

• true if a match is found.
• false if no match is found.

Examples Gallery

Open DevTools Console (F12) or use Try-it links. Examples cover basic checks, validation, negation, case-insensitive matching, and the global-flag lastIndex pitfall.

const regex = /world/;



console.log(regex.test("hello world"));  // true

console.log(regex.test("hello there")); // false

true

false

const emailRule = /^\w+@\w+\.\w+$/;



console.log(emailRule.test("ada@example.com")); // true

console.log(emailRule.test("not-an-email"));    // false

console.log(emailRule.test("a@b.c"));           // true

true

false

true

const digitsOnly = /^\d+$/;



function validateAge(value) {

  if (!digitsOnly.test(value)) {

    return "Age must be digits only.";

  }

  return "OK";

}



console.log(validateAge("42"));     // OK

console.log(validateAge("42abc"));  // Age must be digits only.

OK

Age must be digits only.

const regex = /hello/i;



console.log(regex.test("hello world"));  // true

console.log(regex.test("HELLO World"));  // true

console.log(regex.test("hi there"));     // false

true

true

false

const regex = /a/g;



console.log(regex.test("aba"));  // true  — match at index 0

console.log(regex.test("aba"));  // true  — match at index 2

console.log(regex.test("aba"));  // false — lastIndex past end



regex.lastIndex = 0;

console.log(regex.test("aba"));  // true  — reset works

true

true

false

true

🚀 Common Use Cases

• Form validation — check emails, phone shapes, ZIP codes, and passwords.
• Guard clauses — early-return when input fails a required pattern.
• Filtering arrays — items.filter(item => /pat/.test(item)).
• Feature detection in text — does a log line contain ERROR or WARN?
• File type checks — test extensions like /\.pdf$/i.
• Permission flags — quick pattern checks before heavier parsing with exec().

Important Considerations

• Partial vs full match — without ^…$, test() succeeds on substring matches.
• Global flag side effect — g and y update lastIndex on each call.
• No capture data — use exec() when you need groups or matched text.
• Not a security boundary — regex validation alone does not sanitize HTML or prevent injection.
• Reuse shared regexes — reset lastIndex on global objects before a fresh scan.
• Overly complex patterns — keep validation regex readable; split complex rules into steps.

📝 Notes

• test() is implemented in terms of exec() internally—it discards match details.
• Previous topic: exec() for full match data.
• Next topic: compile() legacy method.
• For whole-field rules, pair with ^ and $ anchors.
• See g modifier for global matching behavior.
• String methods like includes() work for literal text; use regex when patterns are needed.

💡 Best Practices