Looking at the generated command from the Neotest output, it looks like the entire --testNamePattern argument is surrounded by double quotes. Double quotes are interpreted distinctly by the shell in that they allow for certain substitution, such as variable substitution and command output substitution. The single quotes after the = are just interpreted as literal characters, so the text they enclose is still considered surrounded by double quotes.

jest "--no-coverage" "--testLocationInResults" "--verbose" "--json" "--outputFile=/var/folders/7v/zybwdxz140n76nc
dnrtyy80m0000gn/T/nvim.12345/YzZrTS/78.json" "--testNamePattern='^request\\(\\) sets request body directly with data option$'" "<filename>"

I might be wrong (please correct me if I am) but I believe this will be fixed by the PR (#112) which I raised for #47.

This seems to have been fixed at some point — I made a PR (#117) with regression tests just to be sure.

@conermurphy #112 seems to fix tests that use backticks instead of single- or double-quotes for a JavaScript test string — e.g. `this is a test`. This issue is about backticks being present in the test string itself — e.g. "this is a `test`".

Ah that makes sense then @loqusion I did notice that the backticks in strings was working when I did #112 but they must have been fixed by the earlier PR before I did that one.

Also unrelated but I assume you have the tests running locally to make that PR? If so, would you be able to help with #114 at all? I'm keen to write tests when I contribute but can't get them running.

I actually can't get the script to run either 😅 instead, I used the lazy.nvim dev field to use the local development version of neotest-jest to run the tests.

Ah okay so you just ran the jest tests in the repo using neotest itself? Might have to give that a shot. I wonder what's wrong with the script or what extra setup is needed? 🤔