We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test Explorer should list down parameterized tests independently and run them correctly
Test explorer only shows and runs the first test and it also breaks when you try to include parameters in the test name.
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
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
The text was updated successfully, but these errors were encountered:
Same issue here.
Sorry, something went wrong.
Having the exact same issue. Are there any plans to look at this? Seems like quite a large limitation to running jest tests in Visual Studio.
No branches or pull requests
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.
Steps to Reproduce
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
The test explorer shows that the test still passes, which is because it seems to only run the first test
then the test fails in test explorer and test explorer doesn't show it correctly
The text was updated successfully, but these errors were encountered: