Holger Benl

> [2020-01-16 11:09:35.002] [DEBUG] Using config file: c:\Source\Master\App\AppSFSvc\ClientApp\e2e\tsconfig.e2e.json It looks like you set `jasmineExplorer.config` to point to your Typescript configuration instead of your Jasmine configuration (usually called `jasmine.json`).

Now it seems that `jasmineExplorer.config` points to a file in VS Code's data folder, not in your workspace. The reason why changing the code of the extension didn't work for...

I have finally figured out how to do this and created a [launcher script](https://github.com/hbenl/mocha-explorer-launcher-scripts/blob/master/nyc/index.ts). To use it, add the launcher scripts to your project: ``` npm install --save-dev mocha-explorer-launcher-scripts ```...

> that is not a out-of-the-box solution. Obviously. If there is enough interest, I will integrate it properly. But it works for now, is a good example for the versatility...

@munierujp yes, that should work, but you'll have to use the absolute path to the script as the value for `mochaExplorer.launcherScript`.

That stack trace doesn't actually mean there was an error: this adapter uses stack traces to find the exact locations of the `describe()`/`it()` calls, so it's normal for those traces...

I couldn't reproduce the problem yet, if I add ``` it('should work', () => { }); ``` in the inner `describe` block, it works for me. Are there more tests...

You should be able to see the full test log message by clicking the "Show Log" Code Lens (which only appears when there is a log message to show) or...

@David-Else Yeah, colors would be nice, but unfortunately VS Code currently doesn't support colored text in output channels.

It works for me:  Does it work when you run the tests on the command line?