Phpstorm caches test files about karma-browserify HOT 5 CLOSED

Looking around I found the same issue in browserifast:
https://github.com/cjohansen/karma-browserifast/issues/23

It was closed; waiting for a fix in the plugin.

from karma-browserify.

Based on the linked issue and my understanding of Karma's API, WebStorm is wrong here. Disabling autoWatch and then calling karma.runner.run should only tell connected browsers to execute a test run. I did a little poking around and there really isn't a proper way to address this from our end. karma-bro relies on the fact that watchify efficiently watches the bundle graph and caches it so updates happen quickly. Karma watches the written bundle file and then ensures that updates get loaded by connected browsers and that a test run is executed. Indirectly, karma-bro is triggering the test run.

Click auto-test in the WebStorm Test Run window to enable automatic test rerun: The test will be run 10 seconds after your code was changed, if there are no syntax errors. (JetBrains Docs)

So I guess we could technically use a second config option to enable bundle watching internally even if autoWatch is off. Would be super gross but should work so long as your bundle builds within 10 seconds. I'll work up a quick PR and we can discuss there.

from karma-browserify.

Would be nice to have a workaround.

I found the bug reported in the Webstorm plugin, so hopefully the need is transient. https://youtrack.jetbrains.com/issue/WEB-12496

from karma-browserify.

I assume/hope there's a reason they chose to use their own internal watcher instead of letting chokidar handle it.

from karma-browserify.

Moving to #24

from karma-browserify.