Test with template literal is not working

[micaelmbagira]

If you have such a test

it(`should ${'foo'}`, () => {
});

it will be skipped

The issue has apparently been fixed in jest-editor-support but the fix hasn't landed here. I guess it's just a matter of updating the dependency to the latest version and releasing a new version, is that correct?

[firsttris]

hey @micaelmbagira i guess yes.

[firsttris]

you can easily verify for yourself

clone the repo
update package
npm install
(vscode)
Go to Menu "Run" => "Start Debugging"
open your project with the new vscode instance just open

[micaelmbagira]

@firsttris unfortunately, updating jest-editor-support didn't fix it 😢

[firsttris]

can you check if this is working with version 0.4.33

[micaelmbagira]

@firsttris Still not, unfortunately.

[gilphil]

I can confirm it stil doesn't work. The test will skip as soon a dollar sign is in the description.

it('skip me $' , () => {});

In case. Tested with Windows

[mhartkorn]

With an ` in the test name the console expects additional input on Windows.

$ node "c:/redacted/node_modules/jest/bin/jest.js" "c:/redacted.spec.ts" -c "c:/redacted/jest.config.js" -t "Test `"
>

[mhombach]

I can confirm for the current version, for us the test is skipped if the test-title is contains something like this with those special quotes inside

it('should trigger `onChange` event when value changes', () => {...

The onChange in this case is considered as a bash-command (which doesn't exist) because it's used directly in the commandline.

[tlevesque-ueat]

It also doesn't work if the test name is not a string literal (e.g. describe(MyClass.name, ...) instead of describe('MyClass', ...))

[JJBocanegra]

There is no fix for this yet right? It's happening with template literals, variables and even a single apostrophe only when trying to debug the test.

it(`${variable}`) // Won't work

it(variable) // Won't work

it('It\'s me') // Won't work