I was facing same issue, when trying to use require(‘module_name’) (CommonJS style modules) inside a test case and running it using Karma. The reason was require function is not available to browser (it is undefined). To provide it to browser we can browserify the test js files before Karma runs test case in browser using … Read more
In karma.conf.js: browsers = [‘Chrome’]; In your failing spec: it(‘spec’, function() { debugger; // This is like setting a breakpoint // … }); Run Karma. Go to the newly opened Chrome Browser, open the console and refresh the page. Now in Chrome’s Developer Tools source tab you should see the execution stopped at the debugger.
I know how this can be done! Karma’s terminal output comes from objects called Reporters. Karma ships with some built-in Reporters (they can be found in karma/lib/reporters). Karma is also able to use custom Reporters. You can specify which reporters are used in your project’s karma.config.js file. For example, the ‘dots’ reporter just prints a … Read more
Actually in AngularJS Dependency Injection uses the ‘last wins’ rule. So you can define your service in your test just after including your module and dependencies, and then when service A that you’re testing will request service B using DI, AngularJS will give mocked version of service B. This is often is done by defining … Read more
The answer turns out to be very simple. I am using Chrome to run the karma server. When you first start the karma server an instance of Chrome is started as a maximised window. So naturally you minimise this so you can see your tests running. The problem is that Chrome starves any minimised or … Read more
note: This post was valid by Karma in 2014 Jan 16. I am not certain of the current state of that lib, maybe they fixed their weird configuration logic and added meaningful error messages. If not, then this post can be probably very helpful by fixing configuration issues related to Karma. These kind of errors … 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
I had the same problem. From a related GitHub Issue, I learned that you can extend the inactivity timeout. Set this Karma config option in your gruntfile or karma config file: browserNoActivityTimeout: 100000 I set it to 100 seconds and my tests ran successfully. I don’t know what’s causing the delay.
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
Perhaps this will help someone. The solution, for me, was to make sure angular-mocks.js was loaded before my tests. If you’re not sure, you control the order in karma.conf.js under the following section: // list of files / patterns to load in the browser files: [ // include files / patterns here Next, to get … Read more