Common Jest matchers


Some common Jest matchers to evaluate your code

3 Apr, 2022 · 3 min read

Jest using something called matchers to test different results. These matchers can be used to determine if a criterion is what we expect it to be.

In the previous article we’ve used toBeTruthy and toBeFalsy.

However, there are many different ones we can leverage. In this article, we’ll look at some commonly used ones.

Basic matchers

In its simplest form, we can use the toBe matcher to assume something needs “to be” a specific value.

For example:

test('two plus two is four', () => {
  expect(2 + 2).toBe(4);

This is a calculation where we always expect the result to be four. The same can be used to determine string manipulation.

test('uppercase is correct', () => {

Often we also want to determine if an object is a particular format. For this, we can use the toEqual check.

test('should modify a object', () => {
  const data = { foo: 'bar' };
  data['baz'] = 'fuu';
  expect(data).toEqual({ foo: 'bar', baz: 'fuu' });

Another well-used method is to check if specific criteria are no longer met. Sometimes we don’t know the exact output, but we don’t want the outcome to be something specific.

Let’s say we have a dice, which is zero, and on the roll, it should be anything but zero.

test('roll the dice', () => {
  let dice = 0;

When it comes to Arrays, we might want to check if a specific element is included in the array.

For that, we can use the toContain test.

test('Dont forget the milk', () => {
  const shoppingList = ['coffee', 'eggs', 'milk'];

Determine truthiness

As we saw, we can check for something being true or false, but we have a couple extra truthiness checks.

  • toBeNull: If the output is precisely null
  • toBeUndefined: If the output is precisely undefined
  • toBeDefined: Anything but undefined
  • toBeTruthy: Anything considered true
  • toBeFalsy: Anything considered false

These can be super good to check for specific assertions, and especially to make sure something is not one of these.

Calculating with numbers

So far, we have seen we can use toBe to match specific numbers.

But we can go one step further and even determine to which degree numbers should match.

  • toBeGreaterThan: Should be more significant than a certain number
  • toBeGreaterThanOrEqual: Greater than or equal to certain number
  • toBeLessThan: Less than a certain number
  • toBeLessThanOrEqual: Less than or equal to a certain number
  • toBeCloseTo: For floating points to be close to a specific decimal

String regex matches

Often we only want to match strings based on a specific part. As we might not 100% know the rest of the value.

For this, you can use toMatch. It takes regular regex as its parameter.

test('Test for part of string', () => {

The other way around, we can make sure that a part is not in this string.

test('Make sure nothing went wrong', () => {
  expect('Something went wrong, sorry').not.toMatch(/wrong/);

Note: The above will fail as we do have the word “wrong” in our test case

But there is more!

These are some elementary operations, but it’s not the complete list of operations we can use.

A lot of those are super cool to determine if elements are visible on the screen, so we’ll get into that later.

Which test do you use all the time?

Thank you for reading, and let’s connect!

Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter

Spread the knowledge with fellow developers on Twitter
Tweet this tip
Powered by Webmentions - Learn more

Read next 📖

Testing library asFragment tests

18 Apr, 2022 · 2 min read

Testing library asFragment tests

Changing the default testing container

17 Apr, 2022 · 3 min read

Changing the default testing container

Join 2098 devs and subscribe to my newsletter