You can run and debug tests with Karma right in PhpStorm. You can see the test results in a treeview and easily navigate to the test source from there. Test status is shown next to the test in the editor with an option to quickly run it or debug it.
Open the built-in PhpStorm Terminal (press Alt+F12 or choose View | Tool Windows | Terminal on the main menu) and type one of the following commands at the command prompt:
npm install if Karma and all the required plugins are already defined in package.json.
To install Karma and the required plugins (e.g. karma-jasmine or jasmine-core) as development dependencies
Karma tests are run according to a karma.conf.js configuration file which is generated in the interactive mode. If you already have karma.conf.js in your project, just skip this step. For more details on Karma configuration, see Karma official website.
To create a Karma configuration file
Open the Terminal and start the karma.conf.js generation wizard by typing one of the following depending on your operating system:
For macOS and Linux: ./node_modules/karma/bin/karma init
For Windows: npm install -g karma-cli karma init
Answering the questions of the wizard, specify the testing framework to use and the browsers to be captured automatically. See also Karma Files: Pattern matching.
Running tests
With PhpStorm, you can quickly run a single Karma test right from the editor or create a run/debug configuration to execute some or all of your tests.
To run a single test from the editor Click or in the left gutter and choose Run <test_name> from the pop-up list. You can also see whether a test has passed or failed right in the editor, thanks to the test status icons in the left gutter.
Specify the Node interpreter to use, the location of the karma package, and the path to karma.conf.js.
To run tests via a run configuration
Select the Karma run/debug configuration from the list on the main toolbar and click to the right of the list.
The Karma test server starts automatically without any steps from your side. View and analyze messages from the test server in the Karma Server tab of the Run tool window.
With PhpStorm, you can jump between a file and the related test file. Navigation from a test result in the Test Runner Tab to the test is also supported.
To jump between a file and the related test file Open the file in the editor and choose Go To | Test or Go To | Test Subject on the context menu, or just press Ctrl+Shift+T.
To jump from a test result to the test Select the test name in the Test Runner tab and choose Jump to Source on the context menu. The test file opens in the editor with the cursor placed at the test definition.
Debugging tests
With PhpStorm, you can quickly start debugging a single Karma test right from the editor or create a run/debug configuration to debug some or all of your tests.
To start debugging a single test from the editor Click or in the left gutter and choose Debug <test_name> from the pop-up list.
To launch test debugging via a run/debug configuration
With PhpStorm, you can also monitor how much of your code is covered with Karma tests. PhpStorm displays this statistics in a dedicated tool window and marks covered and uncovered lines visually right in the editor. To monitor coverage, you need to install the karma-coverage package and update karma.conf.js.
To install karma-coverage Open the built-in PhpStorm Terminal (press Alt+F12 or choose View | Tool Windows | Terminal on the main menu) and type npm install --save-dev karma-coverage.
To add karma-coverage definition to the configuration file Open karma.conf.js in the editor and add the following information to it:
Locate the reporters definition and add coverage to the list of values in the format:
reporters:['progress','coverage']
Add a preprocessors definition and specify the coverage scope in the format:
Select the Karma run/debug configuration from the list on the main toolbar and click to the right of the list. Alternatively, use the test icons in the editor to quickly run a specific suite or a test with coverage:
Monitor the code coverage in the Coverage tool window. Note that for Karma tests, the Coverage tool window does not show the Generate Coverage Report toolbar button because a coverage report is actually generated on the disk every time Karma tests are run. The format of a coverage report can be configured in the configuration file, for example:
// karma.conf.jsmodule.exports=function(config){config.set({...// optionally, configure the reportercoverageReporter:{type:'html',dir:'coverage/'}...});};
The following type values are acceptable:
html produces a bunch of HTML files with annotated source code.
lcovonly produces an lcov.info file.
lcov produces HTML + .lcov files. This format is applied by default.
cobertura produces a cobertura-coverage.xml file for easy Hudson integration.
text-summary produces a compact text summary of coverage, typically to the console.
text produces a detailed text table with coverage for all files.
or 
in the left gutter and choose Run <test_name> from the pop-up list. You can also see whether a test has passed or failed right in the editor, thanks to the test status icons 
in the left gutter. 
on the toolbar and select Karma from the list. The Run/Debug Configuration: Karma dialog box opens. 
to the right of the list. 
to the right of the list. 
because a coverage report is actually generated on the disk every time Karma tests are run. The format of a coverage report can be configured in the configuration file, for example: The following