Parse describe blocks

[connectdotz]

Summary

enhance test file parsers (js and typescript) to

• return describe block and hierarchical relationship (vscode-jest #351, #321, #298, , #288, #281, #135)
• add support for template literals as test names (vscode-jest #247)
• add support for parsing string buffers
• fix position inconsistency between typescript and js parsers

Test plan

• all unit tests should pass.
• verified with vscode-jest in local build

[codecov-io]

Codecov Report

Merging #7215 into master will increase coverage by 0.21%.
The diff coverage is 93.66%.

@@            Coverage Diff             @@
##           master    #7215      +/-   ##
==========================================
+ Coverage   67.25%   67.46%   +0.21%     
==========================================
  Files         248      249       +1     
  Lines        9641     9719      +78     
  Branches        3        3              
==========================================
+ Hits         6484     6557      +73     
- Misses       3156     3161       +5     
  Partials        1        1

Impacted Files	Coverage Δ
packages/jest-editor-support/src/index.js	0% <0%> (ø)	⬆️
packages/jest-test-typescript-parser/src/index.js	0% <0%> (ø)	⬆️
...es/jest-editor-support/src/parsers/parser_nodes.js	95.65% <95.65%> (ø)
.../jest-editor-support/src/parsers/babylon_parser.js	96.55% <96.07%> (-2.06%)	⬇️
...t-test-typescript-parser/src/type_script_parser.js	97.87% <97.56%> (-2.13%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 814c929...210374f. Read the comment docs.

[connectdotz]

@orta @seanpoulter @stephtr

Finally find the time to get this long-due feature in. This should help closing quite a few issues and unlock other cool features requested in vscode-jest... please take a look at your earliest convenience, thanks.

[orta]

The tests look like I expect they would here - nice work

It's probably worth changing the lockfile access but other than that it's good from me

[orta]

the file access rights have changed on the lock file:100644 → 100755 might be an issue

[orta]

Related: I have a chat with some of the jest core contributors, and we think it makes sense to move this out into it's own repo so that we can handle our own deploys and not block other PRs. It was in here originally so that we can make sure that the types in the JSON for comms between the extension and jest were stable, and it looks like it's not really changed in a year or so. So I think we're good to migrate it to jest-community, which I'm gonna look at next weekend

[connectdotz]

@orta I completely agree, let's do it. I assume you will also include the jest-test-typescript-parser.

[SimenB]

Yeah, I think that's a great idea!
We should make sure to PR the changes made on the Babel 7 branch, so that work is not lost: #7016

EDIT: Also, make sure to get publish access to those modules

[orta]

So I merged this PR into the new repo ( still working on getting tests passing on there, but a lot of it is green now ) - closing this PR

[kjjgibson]

Where can I follow this issue? I'd love to add a debug code lense to describe blocks in vscode-jest but I'd need the describe block parsing first.

[seanpoulter]

I don't think there is an issue to follow anymore @kjjgibson. The PR was merged in jest-community/jest-editor-support.

[kjjgibson]

Aha I see, thanks @seanpoulter. I guess vscode-jest needs to be updated to use the new jest-editor-support instead of the package removed from jest in v24.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.