Open peabnuts123 opened 8 years ago
Same behaviour with Firefox
I have the same behavior as peabnuts123. When I specify PhantomJS and Chrome in karma.conf.js, I see the greyed out tests. But when I do "karma start" in a CMD window, the tests are run and pass. If I remove PhantomJS, they shows as run and succeeded in VS. I have VS2015 Update 1. I don't always get the greyed out behavior. I get it half the time and I had not been able to determine which type of tests it occurs with.
It seams that the problem is in JsTestAdapter. I managed to fix it locally under this post:
https://github.com/MortenHoustonLudvigsen/JsTestAdapter/issues/2
Apologies for not having a screenshot at hand but the issue I've faced is fairly simple to describe. The extension installs without issue and integrates with Karma fine (as long as the
karma.conf.js
is actually included in the.csproj
- which should probably be documented somewhere; different issue). When running jasmine tests in Chrome everything works seamlessly and great. However, when using PhantomJS to launch tests, anything that does not come back as a success gets grayed out by the test explorer, normally a symptom of a test not having been run. The icon stays as whatever it last was, i.e. if it's ever passed then it will stay with a Tick and just toggle on/off depending on whether it passes. This is semi useful but a test not reporting why it failed is incredibly limiting to the value added by a testing framework.If I run
karma start
from the command line everything appears to work fine. It reports failures and successes normally. Apologies I do not have the ability to take an exact output of this at present but can post it later if it would be beneficial.Packages used to run phantomjs:
A few details about my System: