How To Add Unit Tests To Your Strapi Plugin

Testing is a very important part of software development. It allows you to ensure that your code is working as expected and that it will continue to work as expected in the future. In this article, we'll be looking at how to add unit tests using the Jest testing framework to your Strapi plugin.

The code for this tutorial is based on a simple todo plugin which you can find here

If you want to follow along with the same example without the completed test code, use this repo

Prerequisites

To follow along with this post you will need the following

• A v4 Strapi Plugin
• Understanding of Javascript
• Understanding of Strapi
• A basic understanding of Jest
• Git and GitHub (Required for Actions)

What Is Jest

Jest is a testing framework for Javascript. It is a very popular testing framework and is used by many large companies such as Facebook, Airbnb, and Netflix. Jest is a very powerful testing framework and has many features that make it easy to write tests. Jest is also very fast and can run tests in parallel.

Unit tests are aimed at testing individual parts of your code. They are used to ensure that your code is working as expected. Unit tests are very important as they allow you to ensure that your code is working as expected and that it will continue to work as expected in the future.

Installing Jest

To install Jest, run the following command in your terminal

npm install --save-dev jest

or

yarn add --dev jest

Then in your package.json file add the following

1{
2  "scripts": {
3    "test": "jest"
4  }
5}

Configuring Jest

Jest has a lot of global configuration variables but for the purpose of this tutorial, we are going to leave everything as the default. If you want to learn more about how to configure Jest, you can read the Jest documentation. First, we are going to create a new folder to store all of our tests, you should create this in the root of your application and the name is tests.

All tests are going to end with .test.js (or .test.ts). We can go ahead and create our first test file. Create a new file called tests/todo-controller.test.js and add the following code to it.

Creating Our First Test Suite

In ./server/controllers/todo-controller.js we have a very simple controller:

1module.exports = ({ strapi }) => ({
2  async index(ctx) {
3    const { name } = ctx.request.body
4    await strapi.plugin('todo').service('create').create({ name })
5    return ctx.body = 'created'
6  },
7  async complete(ctx) {
8    const { id } = ctx.request.body
9    await strapi.plugin('todo').service('complete').complete({ id })
10    return ctx.body = 'todo completed'
11  },
12})

This controller allows us to create a todo and complete a todo. We are going to write two tests, one for each of these functions.

To create our first test suite we are going to create a new file called tests/todo-controller.test.js and add the following code to it.

1let todoController = require('../server/controllers/todo-controller');
2
3describe('Todo Controller', () => {
4  it('should create a todo', async function () {
5    // TODO: Write test
6  })
7})

We want to import the todoController so that we can call the functions that we want to test. We then create a test suite called Todo Controller and then we create a test called should create a todo. We are going to write our test inside of the it function.

Creating Our First Test

We are going to create a test to test the index function. When making a unit test it's easiest to test pure functions (i.e functions that don't call other functions) however we have a different service that we are calling in our index function. We are going to use a mock function to mock the service that we are calling.

Mocking the Strapi Object

Because we are only testing the index function we are just going to mock any external calls. You typically want to do this for any functions that are being called.

To mock the strapi object we are going to use the jest.mock function. We are going to mock the strapi.plugin('todo').service('create').create function. We are going to mock this function so that we can test that it is being called with the correct arguments.

We don't need to mock up the entire strapi object only the parts that are being used in this function. Since we are going to have multiple tests we want to reset the strapi object every time we run a test. To do this we are going to use the beforeEach function. This function will run before every test and will reset the strapi object.

Within your describe function call beforeEach() with a async function as a callback parameter.

1let todoController = require('../server/controllers/todo-controller');
2
3describe('Todo Controller', () => {
4  let strapi
5  beforeEach(async function () {
6    // mock this teh strapi object to allow for calling of create  await strapi.plugin('todo').service('create').create({ name })
7    strapi = {
8      plugin: jest.fn().mockReturnValue({
9        service: jest.fn().mockReturnValue({
10          create: jest.fn().mockReturnValue({
11            data: {
12              name: 'test',
13              status: false,
14            }
15          }),
16          complete: jest.fn().mockReturnValue({
17            data: {
18              id: 1,
19              status: true,
20            }
21          })
22
23        })
24      })
25    }
26  })
27  it('should create a todo', async function () {
28    // TODO: Write test
29  })
30})

As you can see we are mocking plugin(), service() and create(). We are also returning a mock object from create()

Mocking Request ctx

Now that we mocked up the strapi object we need to mock the ctx object. The ctx object is the request object that is passed into the controller. Because each test is going to have a different ctx object we are going to mock it within each test instead of mocking it globally.

Within our it() function add this code

1 it('should create a todo', async function () {
2    const ctx = {
3      request: {
4        body: {
5          name: 'test'
6        }
7      },
8      body: null
9    }
10  })

This ctx object mimics the ctx object that would be passed into the controller if we were actually running strapi.

Extending Mocking to Your Code

This is a very simplistic example of mocking the strapi and ctx object but as a rule, you should look through your code and mock any external calls that you are making. This will allow you to test your code without having to worry about external calls. Remember it may also be easier to re-arrange your code so that you are testing pure functions.

Calling the Controller

Now that we have mocked the strapi and ctx objects we can call the controller. We are going to call the index() function and pass in the ctx object.

1  it('should create a todo', async function () {
2    const ctx = {
3      request: {
4        body: {
5          name: 'test'
6        }
7      },
8      body: null
9    }
10    // call the index function
11    await todoController({strapi}).index(ctx)
12    // expect the body to be 'created'
13    expect(ctx.body).toBe('created')
14    // expect create to be called once
15    expect(strapi.plugin('todo').service('create').create).toBeCalledTimes(1)
16  })

Here you can see we are passing in our strapi object into the todoController then calling index and passing in the ctx object. We then expect the ctx.body to be created and we expect the strapi.plugin('todo').service('create').create function to be called once.

This means that if down the line the create service isn't being called or if the function is returning a different value then the test will fail.

We can do the same thing for the complete function.

1  it('should complete a todo', async function () {
2    const ctx = {
3      request: {
4        body: {
5          id: 1
6        }
7      },
8      body: null
9    }
10    // call the index function
11    await todoController({strapi}).complete(ctx)
12    // expect the body to be 'created'
13    expect(ctx.body).toBe('todo completed')
14    // expect create to be called once
15    expect(strapi.plugin('todo').service('complete').complete).toBeCalledTimes(1)
16  })

We also need to add the complete object to our strapi object.

1  beforeEach(async function () {
2    // mock this teh strapi object to allow for calling of create  await strapi.plugin('todo').service('create').create({ name })
3    strapi = {
4      plugin: jest.fn().mockReturnValue({
5        service: jest.fn().mockReturnValue({
6          create: jest.fn().mockReturnValue({
7            data: {
8              name: 'test',
9              status: false,
10            }
11          }),
12          complete: jest.fn().mockReturnValue({
13            data: {
14              id: 1,
15              status: true,
16            }
17          })
18
19        })
20      })
21    }
22  })

Our final test suite should look like this

1let todoController = require('../server/controllers/todo-controller');
2
3describe('Todo Controller', () => {
4  let strapi
5  beforeEach(async function () {
6    // mock this teh strapi object to allow for calling of create  await strapi.plugin('todo').service('create').create({ name })
7    strapi = {
8      plugin: jest.fn().mockReturnValue({
9        service: jest.fn().mockReturnValue({
10          create: jest.fn().mockReturnValue({
11            data: {
12              name: 'test',
13              status: false,
14            }
15          }),
16          complete: jest.fn().mockReturnValue({
17            data: {
18              id: 1,
19              status: true,
20            }
21          })
22
23        })
24      })
25    }
26  })
27  it('should create a todo', async function () {
28    const ctx = {
29      request: {
30        body: {
31          name: 'test'
32        }
33      },
34      body: null
35    }
36    await todoController({strapi}).index(ctx)
37    // expect the body to be 'created'
38    expect(ctx.body).toBe('created')
39    // expect create to be called once
40    expect(strapi.plugin('todo').service('create').create).toBeCalledTimes(1)
41  })
42  it('should complete a todo', async function(){
43    const ctx = {
44      request: {
45        body: {
46          id: 1
47        }
48      },
49      body: null
50    }
51    await todoController({strapi}).complete(ctx)
52    // expect the body to be 'todo completed'
53    expect(ctx.body).toBe('todo completed')
54    // expect complete to be called once
55    expect(strapi.plugin('todo').service('complete').complete).toBeCalledTimes(1)
56  })
57})

Testing Services

Now that we have tested the controller we need to test the services. We are going to test the create service and you can try testing the complete service on your own.

We are going to create a new file called create-service.test.js in the tests folder.

We now need to import our create service and mock the strapi object.

1//testing the create service
2const createService = require('../server/services/create')
3describe('Create Service', () => {
4  let strapi
5  beforeEach(async function () {
6    strapi = {
7      query: jest.fn().mockReturnValue({
8        create: jest.fn().mockReturnValue({
9          data: {
10            name: 'test',
11            status: false,
12          }
13        })
14      })
15    }
16  })
17  it('should create a todo', async function () {
18    //todo
19  })
20})

Because our create() service is calling the strapi.query() function we need to mock that function instead of the strapi.plugin() function like in our controller test suite.

Now we can build out our test, we are testing that a todo is created and is only called once and that the returned name is 'test'

1  it('should create a todo', async function () {
2    const name = 'test'
3    const todo = await createService({ strapi }).create({ name })
4    expect(strapi.query('plugin::todo.todo').create).toBeCalledTimes(1)
5    expect(todo.data.name).toBe('test')
6  })

Again we pass in the mocked strapi object into the createService function and call the create() function. We then expect the strapi.query() function to be called once.

Your final service test suite should look like

1//testing the create service
2const createService = require('../server/services/create')
3describe('Create Service', () => {
4  let strapi
5  beforeEach(async function () {
6    strapi = {
7      query: jest.fn().mockReturnValue({
8        create: jest.fn().mockReturnValue({
9          data: {
10            name: 'test',
11            status: false,
12          }
13        })
14      })
15    }
16  })
17  it('should create a todo', async function () {
18    const name = 'test'
19    const todo = await createService({ strapi }).create({ name })
20    expect(strapi.query('plugin::todo.todo').create).toBeCalledTimes(1)
21    expect(todo.data.name).toBe('test')
22  })
23})

This is a very basic example of how you can test your controllers and services. In reality, you would be testing a lot of error logic and edge cases. If you want to see some more complex example of test check out this forms plugin

Running Tests

To run your tests you can run the following command

npm run test

or

yarn test

Automatically Run Tests with GitHub Actions

If you're working on a large team or you want to make sure your tests are running every time you push to GitHub you can use GitHub Actions to automatically run your tests.

To do this you need to create a new file called .github/workflows/test.yaml and add the following code

1name: 'Tests'
2
3on:
4  pull_request:
5  push:
6jobs:
7  run-tests:
8    name: Run Tests
9    runs-on: ubuntu-latest
10    steps:
11      - uses: actions/checkout@v2
12      - name: Install modules
13        working-directory: ./
14        run: npm ci
15      - name: Run Tests
16        working-directory: ./
17        run: npm run test

This will run your tests every time you push to GitHub or create a pull request.

You can also set up branch protection rules within GitHub to prevent merging to master if your tests are failing. To do this go to your repository settings and click on the Branches tab. Then click on Add rule and select the branch you want to protect. Then select Require status checks to pass before merging. You also want to enable Require a pull request before merging and Include administrators. This will prevent you from merging to master if your tests are failing.

Conclusion

Testing can be very annoying and time-consuming but in the long run, it will save you a lot of time and headaches and maybe even stop production from going down.