Argument 'done' is missing inside test.concurrent

Do you want to request a feature or report a bug?

Feature

What is the expected behavior?

I’d like to be able to use done inside async concurrent tests. Here’s my use case:

import { execFile } from 'child-process-promise';

const pathToMyAwesomeCli = '...';
const projectDirs = ['...', '...'];

describe('my-awesome-cli', () => {
  projectDirs.forEach((projectDir) => {
    test(`correctly works for case project \`${projectName}\``, async (done) => {
      try {
        await execFile(pathToMyAwesomeCli, [], { cwd: projectDir });
        done();
      } catch ({ code }) {
        done.fail(`non-zero exit code ${code}`);
      }
    })
  })
})

The above simplified example works great, but unfortunately the tests execute one after another. When I replace test with test.concurrent to have multiple execFile working in parallel, the done argument is no longer available. This means that I cannot use done() or done.fail() inside a concurrent test. It’d be great if test.concurrent and done could work together.

Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.

jest v22.1.4, node v9.4.0, yarn 1.3.2

[SimenB]

You can do .length on the function btw to count number of arguments. You don’t need toString. That’s how jest itself detects if a done callback should be injected or not

Will definitely involve myself

Wonderful! PRs and issues are most welcome 🙂

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.