Add full support for parametrized tests

[andris-zalitis]

Environment

1. node -v: v11.10.0
2. npm -v: 6.7.0
3. npm ls jest: └── [email protected]
4. Operating system: macOS Mojave

Prerequisite

• are you able to run jest test from command line? yes
• how do you run your tests from command line? (for example: npm run test or node_modules/.bin/jest) npm test

Expected Behavior

When using syntax test.each(table)(name, fn, timeout) described here test status circles show the status of tests and failed test error appears in-line.

Actual Behavior

When using syntax test.each(table)(name, fn, timeout) test status circles are not shown and test errors are not displayed inline.

Workaround

If applying parametrization to describe with describe.each, test status information seems to be showed correctly.

In the image below all three tests should have been marked as failed. As it can be seen, the second does not show any test status information and the third (workaround) seems to work. Since I don't want to wrap all my separate tests into describe.each workaround is not that useful in my case.

[malnor]

Was just looking for the same thing. it.each/test.each does not work, but it would be really helpful if it would. To use describe.each instead is not an applicable workaround for me as it defeats the purpose of having several things to test for one describe.

[dgreene1]

Upvote

[KyranRana]

Upvote and bump 👍

[hakubo]

upvote

[connectdotz]

for people who are interested in this issue, please try v4-alpha that should have addressed this issue.

[DScheglov]

@connectdotz , I'm using vscode-jest-4.0.0-alpha.2.

it seams when there is only one it.each per describe the status is displayed correctly, when two or more the status is ?.

1. node -v: v14.15.4
2. npm -v: 6.14.11
3. npm ls jest or npm ls react-scripts (if you haven’t ejected): [email protected]
4. your vscode-jest settings if customized:
   • jest.pathToJest? not customized
   • jest.pathToConfig? not customized
5. OS: Ubuntu 20.04 (64 bit).
6. Jest Config:

{
    "preset": "ts-jest",
    "testEnvironment": "node",
    "collectCoverage": true,
    "collectCoverageFrom": [
      "src/**/*.ts"
    ]
  }

describe('id', () => {
  it.each([
    [true],
    [false],
  ])('returns %s for %s', value => {
    expect(value).toBe(value);
  });
});
describe('not', () => {
  it.each([
    [true],
    [false],
  ])('%s not equal to reverse', value => {
    expect(!value).not.toBe(value);
  });
});

[connectdotz]

indeed we have some gaps to cover... see #649

[connectdotz]

v4.0.0-alpha.3 is released today. The main change is to support the parameterized tests. Feel free to give this release a try and open new issues if needed...

[DScheglov]

v4.0.0-alpha.3 is released today. The main change is to support the parameterized tests. Feel free to give this release a try and open new issues if needed...

I will try it today some later. Thanks a lot for a quick fix!

[DScheglov]

@connectdotz , hey

Now correctly works only the first in the file it.each:

And I guess the number of test-cases is displayed for whole file.

[connectdotz]

@DScheglov I tried your snippet above and all seems to be fine:

Something else is at play here... which jest version your project is on? I should have mentioned that for parameterized tests to be properly reported, you need to have jest version >= 26.5.0 (see migration notes for alpha.3 release). Otherwise, can you post the relevant debug message from the developer console or OUTPUT channel?

[DScheglov]

@DScheglov I tried your snippet above and all seems to be fine:
Something else is at play here... which jest version your project is on? I should have mentioned that for parameterized tests to be properly reported, you need to have jest version >= 26.5.0 (see migration notes for alpha.3 release). Otherwise, can you post the relevant debug message from the developer console or OUTPUT channel?

Hey, @connectdotz thanks. I had 25.x.x version of jest. Upgrading it to the 26.6.3 helped. Now it works well.
Thank you for your help.