microsoft / microsoft/nodejstools
Jest parameterized tests doesn't run correctly
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.8k
- Forks
- 355
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
Test Explorer should list down parameterized tests independently and run them correctly
Actual Behavior
Test explorer only shows and runs the first test and it also breaks when you try to include parameters in the test name.
- NTVS Version: 1.5.40404.3
- Visual Studio Version: 2022
- Node.js Version: 16.15.1
Steps to Reproduce
- Create a new project using docs : https://docs.microsoft.com/en-us/visualstudio/javascript/tutorial-create-react-app?view=vs-2022
- In app.test.js, added a parameterized jest test.
test.each([
[true, true],
[false, false]
])('dummy test', (a, b) => {
expect(a).toBe(b);
});
-
When I build the project and open test explorer, it was expected to show two tests, but shows a single one

-
If I change the test to something which is expected to fail, like
test.each([
[true, true],
[false, true]
])('dummy test', (a, b) => {
expect(a).toBe(b);
});
The test explorer shows that the test still passes, which is because it seems to only run the first test
- If I change the test name to be something parameterized,
test.each([
[true, true],
[false, false]
])('expect %p to be %p', (a, b) => {
expect(a).toBe(b);
});
then the test fails in test explorer and test explorer doesn't show it correctly

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue from app.test.js in a Visual Studio Test Explorer project using the listed Jest parameterized cases. Start by examining how Test Explorer discovers and runs these tests; done means each parameterized case is listed and executed independently, including tests with parameterized names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- devtools, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100