From f8069ac2b332791d103e6275ac3ba7bedc89b2cf Mon Sep 17 00:00:00 2001 From: Jeff Emery Date: Mon, 15 Nov 2021 16:08:57 -0700 Subject: [PATCH] Add helpful instruction to Troubleshooting section (#794) --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index c03f1ec3e..830e11f40 100644 --- a/README.md +++ b/README.md @@ -591,7 +591,8 @@ If the above did not resolve your issue, please see the [self-diagnosis](#self-d
The extension is not behaving as expected, what is going on? (try self diagnosis) -If your can execute jest tests on command line but vscode-jest was not running as expected, here is what you can do to find out more information: +If you can execute jest tests on command line but vscode-jest was not running as expected, here is what you can do to find out more information: + - [Try configuring the `jest.jestCommandLine`](#jestcommandline) with `yarn test` or `npm run test --`. The extension can auto-config common configurations like create react apps but not custom scripts like [CRACO](https://github.com/gsoft-inc/craco). - You can see jest process output with either one of the methods: - If you uses TestExplorer, you can see color coded jest output from the TestExplorer's Output terminal (the square arrow icon on the top of the Explorer View) - Otherwise you can see the output in "OUTPUT" channel, which is usually named after the workspace folder, such as `Jest (your-workspace-name)`. Or you can click on `Jest` label on status bar to show Jest Output window. This will show you the jest run output and the errors.