You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using my karma.conf.js on its own everything works properly. It is a very simple project with all files in the project root folder. Two typescript files. One with a class, the other with the tests for that class.
I simplified the KarmaTestAdapter.json as much as possible.
Interestingly, if I set Disabled to true, no exception occurs and the following is displayed in the the VS output tab [Tests].
[Karma] [Warning] [ktaGlobal] Karma is disabled in KarmaTestAdapter.json
Reading some of the other issues, I tested this against the Karma stack being installed globally in node, and had the same issue.
Originally, the karma.config.js was written in a style using a JS literal object. I changed this to a valid JSON object, and it failed with the same error.
Any ideas?
The text was updated successfully, but these errors were encountered:
Hi Morten!
Love what you have done with this VS extension.
I am having an issue when introducing a KarmaTestAdapter.json file. The following exception is being logged.
When using my
karma.conf.js
on its own everything works properly. It is a very simple project with all files in the project root folder. Two typescript files. One with a class, the other with the tests for that class.I simplified the
KarmaTestAdapter.json
as much as possible.Interestingly, if I set Disabled to true, no exception occurs and the following is displayed in the the VS output tab [Tests].
[Karma] [Warning] [ktaGlobal] Karma is disabled in KarmaTestAdapter.json
Reading some of the other issues, I tested this against the Karma stack being installed globally in node, and had the same issue.
Originally, the
karma.config.js
was written in a style using aJS literal object
. I changed this to a validJSON object
, and it failed with the same error.Any ideas?
The text was updated successfully, but these errors were encountered: