You can use several techniques here: karma uses minimatch globs for file paths and use can take advantage of that to exclude some paths. As first solution I’d say try to add only the paths of the file to preprocess with the coverage: // karma.conf.js module.exports = function(config) { config.set({ files: [ ‘src/**/*.js’, ‘test/**/*.js’ ], … Read more
I was looking for something similar, and found this: https://github.com/usrz/javascript-karma-verbose-reporter. Generates this kind of output: $ karma start –reporters=verbose Suites and tests results: – the app.router.config module : * contains a router property : ok * configures the router title : ok * should have a login route : ok – the organization module : … Read more
Progress will show the number of tests executed, skipped and total. dots will print a dot for each test executed growl will use the growl tool to report the progress of the testing. Note: you need to install the plugin to use this guy. coverage works together with the coverage pre-processor to generate an HTML … Read more
AFAIK, the previous two answers are correct in that you’ll want to run the tests in a browser; click DEBUG and view the output in the console. Politely contradicting the previous answer, I regularly do this and step-through debug with full variable interaction using Karma. The proper answer to your question, because what you want … Read more
It does seem like this is a very general error, however in my case the problem was either that I didn’t run karma start from the correct folder, or that I didn’t restart it after changing the configuration. I’ll leave this question open and hopefully it can become a resource for others who experience this … Read more
If you are using the Karma/Jasmine stack, use: fdescribe(“when …”, function () { // to [f]ocus on a single group of tests fit(“should …”, function () {…}); // to [f]ocus on a single test case }); … and: xdescribe(“when …”, function () { // to e[x]clude a group of tests xit(“should …”, function () {…}); … Read more