Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Run/debug buttons placed at wrong position & associated with wrong test name

See original GitHub issue

Consider this file:

The buttons are placed at the wrong position in the test, and if I press the Run button, jest will be invoked like this in the console so no tests will be run at all:

node '/workspace/downstream-repository-mining/node_modules/.bin/jest' '/workspace/downstream-repository-mining/test/references\.test\.ts' -t 'getNpmDeps'

Apparently, the heuristic (?) that is used to find the jest cases does not cover my rather uncommon test file here … 😃

Issue Analytics

State:
Created 2 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

LinqLovercommented, Jun 2, 2021

Confirmed. So this is officially a low-level issue.

(Haha, I just noticed that I used the “Jest Test Explorer” for this before. 😃 It does not have such a nice editor integration as this project, but the debugger integration is a bit better IMHO. For example, if I run an expect() assertion in the debugging console, with vscode-jest-runner, I see [2m artifacts in the output, whereas when using “Jest Test Explorer”, jest appears to know that it is not printing to a TTY. Just a notice. 😃)

0reactions

firsttriscommented, Sep 9, 2021

re-open if this issue still persists