We highly recommend working in the style of test-driven development when creating probot apps. It is frustrating to constantly create real GitHub events in order to test an app. Redelivering webhooks is possible and can be accessed in your app’s settings page under the Advanced tab. We do offer the above documented receive method to help make this easier; however, by writing your tests first, you can avoid repeatedly recreating actual events from GitHub to check if your code is working.

For our testing examples, we use jest, but there are other options that can perform similar operations. We also recommend using nock, a tool for mocking HTTP requests, which is often crucial to testing in Probot, considering how much of Probot depends on GitHub’s APIs. Here’s an example of creating an app instance and using nock to test that we correctly hit the GitHub API:

const nock = require('nock')
// Requiring our app implementation
const myProbotApp = require('..')
const { Probot, createProbot } = require('probot')
// Requiring our fixtures
const payload = require('./fixtures/issues.opened')
const issueCreatedBody = { body: 'Thanks for opening this issue!' }

describe('My Probot app', () => {
  let probot

  beforeEach(() => {
    probot = createProbot({ id: 1, cert: 'test', githubToken: 'test' })

  test('creates a passing check', async () => {
    // Test that we correctly return a test token
      .reply(200, { token: 'test' })

    // Test that a comment is posted
      .post('/repos/hiimbex/testing-things/issues/1/comments', (body) => {
        return true

    // Receive a webhook event
    await probot.receive({ name: 'issues', payload })

  afterEach(() => {

A good testing example from dco can be found here, and another one from markdownify can be found here.