Holger Benl

> In this section workspaceFolder is never defined Do you mean the expression `workspaceFolder => new MyTestAdapter(workspaceFolder)`? In that case, the left hand side of the arrow is the declaration...

The adapter needs a communication channel through which Jasmine can report the results of loading or running the tests. The current communication channel would most likely not work with the...

@johnhamm @IGx89 Interestingly, I can't reproduce this problem. In my small test project, it works even with ``` "compilerOptions": { "module": "es2015" } ``` Does adding ``` "jasmineExplorer.env": { "TS_NODE_COMPILER_OPTIONS":...

@supersinex This adapter can't load and run Karma tests, but a Karma adapter is being worked on, see hbenl/vscode-example-test-adapter#1

@apis3445 Can you point me to a sample project with which I can reproduce this?

So are these tests karma or protractor tests? In that case, it won't work with this adapter, but for Karma tests there is the Angular/Karma Test adapter.

I am getting the same error, but I also get it when I run Jasmine from the command line. Which is not surprising, because Jasmine will simply `require('src/test-setup.js')`, which means...

I just realized that using the `requires` property will only work with this adapter to load globally installed packages. I added a configuration option `jasmineExplorer.jasminePath` in version 1.6.0, if you...

@apla Makes sense. I'm just not 100% sure yet how to do that auto-detection: * detecting `jasmineExplorer.jasminePath`: I'd like to also detect a globally installed `jasmine` package, so I'm thinking...

> `npm install` not executed + 3 years old jasmine = high probability of strange errors Good point! So maybe the autodetection should just look for `node_modules/jasmine` after all? That...