James Russo

Engineering at Brex

Fullstack engineer who knows nothing about design.
Example: this website.

Bored Hacking

Mocking Sentry in Jest and Gatsby

September 23, 2019 | 2 min read

When testing a React or more specifically a Gatsby.js application that uses Sentry.io it is necessary to make sure that you mock Sentry. This way you aren’t actually making API calls, and more importantly you should most likely not be loading Sentry in your test environment anyways. So if Sentry is missing or not setup in the testing environment this may cause your tests to fail, raising a ReferenceError: Sentry is not defined. In order to get started adding Sentry to your Gatsby.js project, please follow the great tutorial and use the plugin gatsby-plugin-sentry which you can find here. This is an easy to use plugin to add Sentry to your project and only load it in certain environments, in my case “staging” and “production”.

The next step is to follow another great tutorial on adding Jest to your Gatsby.js application which can be found here. This will go through all of the initial setup to get Jest working with your Gatsby.js application. However if you use the global Sentry object created by gatsby-plugin-sentry in your code this will cause your tests to error out and fail. The solution around this is to mock the global Sentry object so that your tests can pass.

First you must create a new file in your root directory, let’s call it setup-test-env.js. This file can be used to setup globals and other things needed for you Jest tests after the environment has been setup. Then in your jest.config.js you must add the line setupFilesAfterEnv: ["<rootDir>/setup-test-env.js"] like so

// jest.config.js
module.exports = {
  transform: {
    "^.+\\.jsx?$": `<rootDir>/jest-preprocess.js`,
  moduleDirectories: ["node_modules", `<rootDir>`],
  moduleNameMapper: {
    ".+\\.(css|styl|less|sass|scss)$": `identity-obj-proxy`,
    ".+\\.(jpg|jpeg|png|gif|eot|otf|webp|svg|ttf|woff|woff2|mp4|webm|wav|mp3|m4a|aac|oga)$": `<rootDir>/__mocks__/file-mock.js`,
  testPathIgnorePatterns: [`node_modules`, `.cache`],
  transformIgnorePatterns: [`node_modules/(?!(gatsby)/)`],
  globals: {
    __PATH_PREFIX__: ``,
  testURL: `http://localhost`,
  setupFiles: [`<rootDir>/loadershim.js`],
  setupFilesAfterEnv: ["<rootDir>/setup-test-env.js"]

This will ensure that the setup file is loaded in after the enviornment is loaded. This way any needed packages and other values will be setup and loaded in this file.

Now in setup-test-env.js we need to mock Sentry globally so that we can use it in our code run by our tests and not get an error that Sentry is not defined. This can be accomplished with the following line’s of code

// setup-test-env.js
import * as Sentry from '@sentry/browser'

global.Sentry = Sentry

And just like that you should be able to run your tests and mock the global Sentry value so that your code is able to call the global Sentry object without raising any error’s.