The test() method executes a search for a match between a regular expression and a specified string. Returns true or false.




The string against which to match the regular expression.


true if there is a match between the regular expression and the specified string; otherwise, false.


Use test() whenever you want to know whether a pattern is found in a string (similar to the method, difference is that test returns a boolean, whilst search returns the index (if found) or -1 if not found); for more information (but slower execution) use the exec() method (similar to the String.prototype.match() method). As with exec() (or in combination with it), test() called multiple times on the same global regular expression instance will advance past the previous match.


Using test()

Simple example that tests if "hello" is contained at the very beginning of a string, returning a boolean result.

var str = "hello world!";
var result = /^hello/.test(str);
console.log(result); // true

The following example logs a message which depends on the success of the test:

function testinput(re, str){
  var midstring;
  if (re.test(str)) {
    midstring = ' contains ';
  } else {
    midstring = ' does not contain ';
  console.log(str + midstring + re.source);


Specification Status Comment
ECMAScript 3rd Edition (ECMA-262) Standard Initial definition. Implemented in JavaScript 1.2.
ECMAScript 5.1 (ECMA-262)
The definition of 'RegExp.test' in that specification.
ECMAScript 2015 (6th Edition, ECMA-262)
The definition of 'RegExp.test' in that specification.
ECMAScript 2017 Draft (ECMA-262)
The definition of 'RegExp.test' in that specification.

Browser compatibility

Feature Chrome Firefox (Gecko) Internet Explorer Opera Safari
Basic support (Yes) (Yes) (Yes) (Yes) (Yes)
Feature Android Chrome for Android Firefox Mobile (Gecko) IE Mobile Opera Mobile Safari Mobile
Basic support (Yes) (Yes) (Yes) (Yes) (Yes) (Yes)

Gecko-specific notes

Prior to Gecko 8.0 (Firefox 8.0 / Thunderbird 8.0 / SeaMonkey 2.5), test() was implemented incorrectly; when it was called with no parameters, it would match against the value of the previous input (RegExp.input property) instead of against the string "undefined". This is fixed; now /undefined/.test() correctly results in true, instead of an error.

See also

Document Tags and Contributors

 Last updated by: eduardoboucas,