[jest-editor-support]: jest 23.x compatibility

[connectdotz]

Summary

This PR mainly to address jest 23.x compatibility and config parsing issues:

• jest-editor-support in 23.x no longer trigger test results processing due to Use outputStream instead of stdout for output file #4858: jest-community/vscode-jest/316
• Setting parser failed to extract jest settings sometimes, such as in CRA env: jest-community/vscode-jest/337

plus some clean up and self-diagnosis:

• update the typescript typings
• added a debug flag in workspace

Test plan

• added new unit tests
• test vscode-jest:
  • with jest 23.x repo, as well as non 23.x (backward compatible)
  • with CRA js/ts repo to make sure settings are extracted properly.

---

would also like to request @orta, @seanpoulter or @stephtr to review this PR.

[orta]

O, yeah, cool, this looks good to me - yep. I've taken a stab at fixing CI in #6587

[stephtr]

I didn't notice any obvious problems, but my insight into Jest 23 and jest-editor-support is much lower than in vscode-jest.

[connectdotz]

thanks @orta , @stephtr

@orta, looks like #6587 did pass the test-node-6 but somehow failed in continuous-integration/travis-ci/pr, not sure if they are related, do you plan to merge #6587 anyway? or should I just copy your fetchSupporters.js? or we can temporarily ignore test-node-6 as it is not related to this PR?

[orta]

OK, I got merged #6587 - but that doesn't unbreak the build, just moves that fail a bit further up, so I'm going to merge this 👍

[connectdotz]

@cpojer @SimenB is it possible to cut an alpha release so we can unblock vscode-jest users with jest 23.x dependency asap?

[thymikee]

cc @mjesun

[mjesun]

I can make a patch, if @thymikee and @SimenB agree.

[SimenB]

I'd like to rename the prettier option for inline snapshots. Can send a PR within the hour for it. Then we should be good to go :)

Ref #6380 (comment)

[SimenB]

#6607

[SimenB]

Oh, and #6603. CI is weird, should be good to land (I restarted the two CIs)

[mjesun]

@SimenB 👌🏻 Feel free to merge all three (I think you have permissions) and I'll then proceed. This looks however like a minor, though. Are you OK with that?

[SimenB]

Yeah, it's a minor. Will merge and keep a screenshot of your comment if @cpojer comes after me with a torch! 😀

[SimenB]

@mjesun should be ready for release now 🙂

[connectdotz]

thanks for everybody's effort! I checked the release log this morning and it was still at 23.2.0. Is there some other place I should check for the new release?

[mjesun]

@connectdotz was a busy morning, sorry! It's released now :)

[connectdotz]

awesome! 👍

[stephtr]

By the way: When starting up your vscode-jest branch with a CRA app, I always get a "failed to parse config" with text being just (that's the additional output of npm test -- --showConfig):

"
> cra-ts-test@0.1.0 test c:\Users\stroy\Projekte\_Playground\cra-ts-test
> react-scripts-ts test --env=jsdom "--showConfig"
"

However since _parseConfig also gets called with the real settings afterwards, the extensions work without flaw.

[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.