We need to integrate Karma test runner into TeamCity and for that I&#39;d like to give sys-engineers small script (powershell or whatever) that would:

 1. pick up desired version number from some config file (I guess I can put it as a comment right in the `karma.conf.js`)

 2. check if the defined version of karma runner installed in npm&#39;s global repo

 3. if it&#39;s not, or the installed version is older than desired: pick up and install right version

 4. run it: `karma start .\Scripts-Tests\karma.conf.js --reporters teamcity --single-run `

So my real question is: &quot;how can one check in a script, if desired version of package installed?&quot;. Should you do the check, or it&#39;s safe to just call `npm -g install` everytime?

*I don&#39;t want to always check and install the latest available version, because other config values may become incompatible*

npm check and update package if needed

What is the use of `chore` in [semantic version control commit messages](http://seesparkbox.com/foundry/semantic_commit_messages)? Other types like **feat** or **fix** are clear, but I don&#39;t know when to use &quot;chore&quot;.

Can anyone provide a couple of examples of its use?

Another maybe not related question: What&#39;s the proper type of messages of commits for modifying files like `.gitignore`?



When to use &quot;chore&quot; as type of commit message?

Is there a way to run `ng test` for a single file instead of for the entire test suite?  Ideally, I&#39;d like to get the quickest possible feedback loop when I&#39;m editing a file, but `karma` executes the whole suite on each save, which is a bit slow when you build up a big enough test suite.

---

This is different from https://stackoverflow.com/questions/40683673/how-to-execute-only-one-test-spec-with-angular-cli in that that question is about running an individual spec.  This is about running an individual file.  The solution involves the same Jasmine spec feature, but the nature of the question is slightly different.

Running a single test file

I&#39;ve been trying to run an npm install on my package.json file, but I&#39;m having a lot of trouble.  It keeps saying &quot;Error:  Attempt to unlock XXX, which hasn&#39;t been locked&quot; on all my dependences.  Here&#39;s one of them:

    Error: Attempt to unlock tbd@~0.6.4, which hasn&#39;t been locked
            at unlock (/usr/local/lib/node_modules/npm/lib/cache.js:1304:11)
            at cb (/usr/local/lib/node_modules/npm/lib/cache.js:646:5)
            at /usr/local/lib/node_modules/npm/lib/cache.js:655:20
            at /usr/local/lib/node_modules/npm/lib/cache.js:1290:7
            at /usr/local/lib/node_modules/npm/node_modules/lockfile/lockfile.js:167:38
            at OpenReq.Req.done (/usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:144:5)
            at OpenReq.done (/usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:64:22)
            at Object.oncomplete (fs.js:107:15)

If I try to run it as sudo, it seems to get further and start installing some packages, but some new errors popup instead:

    &gt; chokidar@0.8.1 postinstall /Users/tkirchner/Documents/Projects/mm-datatable/node_modules/karma/node_modules/chokidar
    &gt; node setup-deps.js
    
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: Permission denied
    
    node.js:811
        var cwd = process.cwd();
                          ^
    Error: EACCES, permission denied
        at Function.startup.resolveArgv0 (node.js:811:23)
        at startup (node.js:58:13)
        at node.js:902:3
    npm ERR! error rolling back Error: ENOTEMPTY, rmdir &#39;/Users/tkirchner/Documents/Projects/mm-datatable/node_modules/karma/node_modules/q&#39;
    npm ERR! error rolling back  karma@0.10.9 { [Error: ENOTEMPTY, rmdir &#39;/Users/tkirchner/Documents/Projects/mm-datatable/node_modules/karma/node_modules/q&#39;]
    npm ERR! error rolling back   errno: 53,
    npm ERR! error rolling back   code: &#39;ENOTEMPTY&#39;,
    npm ERR! error rolling back   path: &#39;/Users/tkirchner/Documents/Projects/mm-datatable/node_modules/karma/node_modules/q&#39; }
    npm ERR! Error: ENOENT, chown &#39;/Users/tkirchner/Documents/Projects/mm-datatable/node_modules/karma/node_modules/socket.io/lib/socket.io.js&#39;

I recently updated my node and npm installations.  So maybe that has something to do with it.  Also, most of my development has been at the office and today I&#39;m working over VPN, so maybe that has something to do with it too.

Any ideas?

NPM cannot install dependencies - Attempt to unlock something which hasn&#39;t been locked

I am trying to run the default service unit test in my project (Taken from the Angular Seed project on GitHub), but I keep getting the error &quot;module is not defined&quot;.

I have read that it could be something to do with the order of the [referenced JavaScript files][1], but I can&#39;t seem to get it to work, so hopefully one of you might be able to help.

My configuration for the test looks like this:

&gt; basePath = &#39;../&#39;;
&gt; 
&gt; files = [   
&#39;public/javascripts/lib/jquery-1.8.2.js&#39;,  
&gt; &#39;public/javascripts/lib/angular.js&#39;,  
&gt; &#39;public/javascripts/lib/angular-*.js&#39;,   
&gt;  &#39;public/app.js&#39;,  
&gt; &#39;public/controllers/*.js&#39;,   
&#39;public/directives.js&#39;,  
&gt; &#39;public/filters.js&#39;,   
&#39;public/services.js&#39;,   
JASMINE,  
&gt; JASMINE_ADAPTER,   
&#39;public/javascripts/lib/angular-mocks.js&#39;,  
&gt; &#39;test/unit/*.js&#39; ];
&gt; 
&gt; autoWatch = true;
&gt; 
&gt; browsers = [&#39;Chrome&#39;];
&gt; 
&gt; junitReporter = {   outputFile: &#39;test_out/unit.xml&#39;,   suite: &#39;unit&#39;
&gt; };


The service looks like the following:

    angular.module(&#39;myApp.services&#39;, []).
      value(&#39;version&#39;, &#39;0.1&#39;);


The test looks like this:

    &#39;use strict&#39;;
       
    describe(&#39;service&#39;, function() {
      beforeEach(module(&#39;myApp.services&#39;));
    
    
      describe(&#39;version&#39;, function() {
        it(&#39;should return current version&#39;, inject(function(version) {
          expect(version).toEqual(&#39;0.1&#39;);
        }));
      });
    });

And the error when running the test through testacular is this:

&gt; ReferenceError: module is not defined


  [1]: https://github.com/vojtajina/testacular/issues/66

Testing service in Angular returns module is not defined

I&#39;m developing a [github repository][1] (with angular 7 and angular-cli), and I have some tests with Karma and Jasmine working in the master branch.

Now I&#39;m trying to add lazy loading feature, the thing is, that the tests that before passed, now they do not. It&#39;s funny because only the tests from the lazy loading module are failing...

Here is the code and the error:

    import {async, TestBed} from &#39;@angular/core/testing&#39;;
    import {APP_BASE_HREF} from &#39;@angular/common&#39;;
    import {AppModule} from &#39;../../app.module&#39;;
    import {HeroDetailComponent} from &#39;./hero-detail.component&#39;;

    describe(&#39;HeroDetailComponent&#39;, () =&gt; {
      beforeEach(async(() =&gt; {
        TestBed.configureTestingModule({
          imports: [AppModule
          ],
          providers: [
            {provide: APP_BASE_HREF, useValue: &#39;/&#39;}
          ],
        }).compileComponents();
      }));

      it(&#39;should create hero detail component&#39;, (() =&gt; {
        const fixture = TestBed.createComponent(HeroDetailComponent);
        const component = fixture.debugElement.componentInstance;
        expect(component).toBeTruthy();
      }));
    });

The error is this:

    Chrome 58.0.3029 (Mac OS X 10.12.6) HeroDetailComponent should create hero detail component FAILED
        Error: Illegal state: Could not load the summary for directive HeroDetailComponent.
            at syntaxError Users/ismael.ramos.silvan/WebstormProjects/angular4-example-app/~/@angular/compiler/@angular/compiler.es5.js:1690:22)
            at CompileMetadataResolver.getDirectiveSummary Users/ismael.ramos.silvan/WebstormProjects/angular4-example-app/~/@angular/compiler/@angular/compiler.es5.js:15272:1)
            at JitCompiler.getComponentFactory Users/ismael.ramos.silvan/WebstormProjects/angular4-example-app/~/@angular/compiler/@angular/compiler.es5.js:26733:26)
            at TestingCompilerImpl.getComponentFactory Users/ismael.ramos.silvan/WebstormProjects/angular4-example-app/~/@angular/compiler/@angular/compiler/testing.es5.js:484:1)
            at TestBed.createComponent Users/ismael.ramos.silvan/WebstormProjects/angular4-example-app/~/@angular/core/@angular/core/testing.es5.js:874:1)
            at Function.TestBed.createComponent Users/ismael.ramos.silvan/WebstormProjects/angular4-example-app/~/@angular/core/@angular/core/testing.es5.js:652:1)
            at UserContext.it Users/ismael.ramos.silvan/WebstormProjects/angular4-example-app/src/app/heroes/hero-detail/hero-detail.component.spec.ts:18:29)
            at ZoneDelegate.webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.invoke Users/ismael.ramos.silvan/WebstormProjects/angular4-example-app/~/zone.js/dist/zone.js:391:1)
            at ProxyZoneSpec.onInvoke Users/ismael.ramos.silvan/WebstormProjects/angular4-example-app/~/zone.js/dist/proxy.js:79:1)
            at ZoneDelegate.webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.invoke Users/ismael.ramos.silvan/WebstormProjects/angular4-example-app/~/zone.js/dist/zone.js:390:1)

You can see the entire project, for more details if you need it.

**UPDATE: added declaration like this:**

    beforeEach(async(() =&gt; {
        TestBed.configureTestingModule({
          imports: [
            AppModule
          ],
          declarations: [HeroDetailComponent],
          providers: [
            {provide: APP_BASE_HREF, useValue: &#39;/&#39;}
          ],
        }).compileComponents();
      }));

Now, new errors appears:

    The pipe &#39;translate&#39; could not be found (&quot;&lt;h1 class=&quot;section-title&quot;&gt;{{[ERROR -&gt;]&#39;heroDetail&#39; | translate}}&lt;/h1&gt;
        &lt;md-progress-spinner *ngIf=&quot;!hero&quot;
                             class=&quot;progre&quot;): ng:///DynamicTestModule/HeroDetailComponent.html@0:28
        Can&#39;t bind to &#39;color&#39; since it isn&#39;t a known property of &#39;md-progress-spinner&#39;.

And more... it&#39;s like all directives and components from angular material, and the pipe translate from ngx-translate/core do not appear to be included...


  [1]: https://github.com/Ismaestro/angular4-example-app
  [2]: https://github.com/Ismaestro/angular4-example-app/tree/feature/lazy-loading

Angular Karma Jasmine Error: Illegal state: Could not load the summary for directive

Hi I am trying to unit test while developing a simple web with AngularJS + Firebase, but I have a problem defining the spec and trying the test runner

myProject/test/spec/main.js :

    describe(&#39;Controller: MainCtrl&#39;, function() {
	
	var MainCtrl, scope
	
	beforeEach(module(&#39;MainApp&#39;));

	beforeEach(inject(function ($controller, $rootScope) {
		scope = $rootScope.$new();
		MainCtrl = $controller(&#39;MainCtrl&#39;, {
			$scope: scope
		})
	}));

	it(&#39;should....&#39;,function(){
		expect(true).toBe(true)
	})
	it(&#39;should2....&#39;,function(){
		expect(false).toBe(false)
	})
    });

result:

    PhantomJS 2.1.1 (Mac OS X 0.0.0) Controller: MainCtrl should.... FAILED
    Error: [$injector:modulerr] Failed to instantiate module MainApp due 
    to: Firebase: Firebase App named &#39;[DEFAULT]&#39; already exists 
    (app/duplicateapp).

However, defining the spec once is not a problem. For example:

    it(&#39;should....&#39;,function(){
       expect(true).toBe(true)
    })

I do not know why this is the reason I give a hint to me

Here is the project I am developing.

https://github.com/parkwookyun/firebase-angular-board


Firebase App named &#39;[DEFAULT]&#39; already exists (app/duplicate-app)

I&#39;m trying to run karma as part as an *angular-seed* project, after installing karma using

    npm install -g karma

I get:

    &#39;karma&#39; is not recognized as an internal or external command, operable program or batch file.

when i&#39;m trying to run test.bat from angular-client\scripts, the content of this file is:

&gt; set BASE_DIR=%~dp0
&gt;
&gt;karma start &quot;%BASE_DIR%\..\config\karma.conf.js&quot; %*

I also tried to navigate to &quot;\AppData\Roaming\npm\node_modules\karma\bin&quot; and saw karma file, when I&#39;m trying to run it I get again:

&gt;  &#39;karma&#39; is not recognized as an internal or external command, operable program or batch file.

Any suggestions? 
If not please suggest how to use jasmine without karma.

Thanks.

Running karma after installation results in &#39;karma&#39; is not recognized as an internal or external command

If [Protractor][1] is replacing Angular Scenario Runner for E2E testing, does that mean I will still be able to use it with [Karma][2] as my E2E testing framework ?


  [1]: https://github.com/juliemr/protractor
  [2]: https://github.com/karma-runner/karma

Can Protractor and Karma be used together?

So, I&#39;ve been looking all over for this, found &quot;similar&quot; answers here, but not exactly what I want.

Right now if I want to test a single file with karma, I need to do `fit()`, `fdescribe()` on the file in question...

However, what I do want is to be able to just call karma, with the config file, and direct it to a specific file, so I don&#39;t need to modify the file at all, ie:

`karma run --conf karma.conf.js --file /path/to/specific/test_file.js`

is it possible to do this? Or with any helper? (using grunt or gulp?)

Karma: Running a single test file from command line

I am trying to test my route resolver and while testing I got `TypeError: ctor is not a constructor` and no idea why it happen while typescript compile time no error.

    TypeError: ctor is not a constructor
    TypeError: ctor is not a constructor
        at _createClass (http://localhost:9877/_karma_webpack_/vendor.bundle.js:42355:26)
        at _createProviderInstance$1 (http://localhost:9877/_karma_webpack_/vendor.bundle.js:42330:26)
        at resolveNgModuleDep (http://localhost:9877/_karma_webpack_/vendor.bundle.js:42315:17)
        at _createClass (http://localhost:9877/_karma_webpack_/vendor.bundle.js:42362:26)
        at _createProviderInstance$1 (http://localhost:9877/_karma_webpack_/vendor.bundle.js:42330:26)
        at resolveNgModuleDep (http://localhost:9877/_karma_webpack_/vendor.bundle.js:42315:17)
        at NgModuleRef_.webpackJsonp../node_modules/@angular/core/@angular/core.es5.js.NgModuleRef_.get (http://localhost:9877/_karma_webpack_/vendor.bundle.js:43401:16)
        at TestBed.webpackJsonp../node_modules/@angular/core/@angular/core/testing.es5.js.TestBed.get (http://localhost:9877/_karma_webpack_/vendor.bundle.js:48412:47)
        at http://localhost:9877/_karma_webpack_/vendor.bundle.js:48418:61
        at Array.map (native)

angular 4 unit testing error `TypeError: ctor is not a constructor`

I&#39;m trying to add some unit tests to one of my projects.

So far I&#39;ve installed and configured karma, and have installed jasmine. I&#39;ve one test file in my `test/` folder.

The karma server has started, the browser page is ready, but `karma run` fails as follows:

    $ karma run karma-conf.js 
    [2014-06-14 15:19:11.046] [DEBUG] config - Loading config /foo/test/karma-conf.js
    Waiting for previous execution...
    Chrome 35.0.1916 (Linux) ERROR
      You need to include some adapter that implements __karma__.start method!

This error message doesn&#39;t Google well.

Is this something obvious, or do I need to provide more information?

Error: You need to include some adapter that implements __karma__.start method

I use karma to run tests. I have many tests and running all tests is a very slow process. I want to run only a single test in order to spend less time, because all tests are run about 10 minutes.

Is it possible?

Karma run single test

I&#39;m unit testing one of my directives (angularjs) using grunt/karma/phantomjs/jasmine. My tests run fine

    describe(&#39;bar foo&#39;, function () {
        beforeEach(inject(function ($rootScope, $compile) {
            elm = angular.element(&#39;&lt;img bar-foo src=&quot;img1.png&quot;/&gt;&#39;);
            scope = $rootScope.$new();
            $compile(elm)();
            scope.$digest();
        }));
        ....
    });

but I do get these 404s 

    WARN [web-server]: 404: /img1.png
    WARN [web-server]: 404: /img2.png
    ...

Although they do nothing, they do add noise to the log output. Is there a way to fix this ? (without changing karma&#39;s logLevel of course, because I do want to see them)


how to fix 404 warnings for images during karma unit testing

How do I setup Karma to run my backend unit tests (written with Mocha)? If I add my backend test script to the `files = []`, it fails stating that `require` is undefined.

How to test nodejs backend code with Karma (testacular)

I have an AngularJS app set up with tests using Karma+Jasmine. I have a function I want to test that takes a large JSON object, converts it to a format that&#39;s more consumable by the rest of the app, and returns that converted object. That&#39;s it.

For my tests, I&#39;d like you have separate JSON files (*.json) with mock JSON content only--no script. For the test, I&#39;d like to be able to load the JSON file in and pump the object into the function I&#39;m testing.

I know I can embed the JSON within a mock factory as described here: http://dailyjs.com/2013/05/16/angularjs-5/ but I really want the JSON to not be contained within script--just straight JSON files.

I&#39;ve tried a few things but I&#39;m fairly noob in this area. First, I set up my Karma to include my JSON file just to see what it would do: 

    files = [
        ...
        &#39;mock-data/**/*.json&#39;
        ...
    ]

This resulted in:

    Chrome 27.0 (Mac) ERROR
    Uncaught SyntaxError: Unexpected token :
    at /Users/aaron/p4workspace4/depot/sitecatalyst/branches/anomaly_detection/client/anomaly-detection/mock-data/two-metrics-with-anomalies.json:2


So then I changed it to just serve the files and not &quot;include&quot; them: 

    files = [
        ...
        { pattern: &#39;mock-data/**/*.json&#39;, included: false }
        ...
    ]

Now that they&#39;re only served, I thought I&#39;d try to load in the file using $http from within my spec:

    $http(&#39;mock-data/two-metrics-with-anomalies.json&#39;)

When I ran the spec I received:

    Error: Unexpected request: GET mock-data/two-metrics-with-anomalies.json

Which in my understanding means it expects a mocked response from $httpBackend. So...at this point I didn&#39;t know how to load the file using Angular utilities so I thought I&#39;d try jQuery to see if I could at least get that to work:

    $.getJSON(&#39;mock-data/two-metrics-with-anomalies.json&#39;).done(function(data) {
        console.log(data);
    }).fail(function(response) {
        console.log(response);
    });

This results in:

    Chrome 27.0 (Mac) LOG: { readyState: 4,
    responseText: &#39;NOT FOUND&#39;,
    status: 404,
    statusText: &#39;Not Found&#39; }

I inspect this request in Charles and it&#39;s making a request to

    /mock-data/two-metrics-with-anomalies.json

Whereas the rest of the files I&#39;ve configured to be &quot;included&quot; by Karma are being requested at, for example:

    /base/src/app.js

Apparently Karma&#39;s setting up some sort of base directory to serve the files from. So for kicks I changed my jquery data request to

    $.getJSON(&#39;base/mock-data/two-metrics-with-anomalies.json&#39;)...

And it works! But now I feel dirty and need to take a shower. Help me feel clean again.

Loading a mock JSON file within Karma+AngularJS test

When unit testing an Angular factory (with Karma + Jasmine), how do I inject a stub dependency into the factory under test?

Here&#39;s my factory:

    mod = angular.module(&#39;myFactoryMod&#39;, []);

    mod.factory(&#39;myFactory&#39;, [
      &#39;$log&#39;, &#39;oneOfMyOtherServices&#39;, function($log, svc) {
        return makeSomethingThatDoesSomethingWithTheseDependencies($log, svc);
      }
    ]);


`oneOfMyOtherServices` is needed when instantiating my factory.

Here&#39;s my test:

    it(&#39;can get an instance of my factory&#39;, function() {
      var oneOfMyOtherServicesStub;
    
      angular.mock.module(&#39;myFactoryMod&#39;);
    
      oneOfMyOtherServicesStub = {
        someVariable: 1
      };
    
      //****How do I get my stub in my target? ****
    
      angular.mock.inject([&#39;myFactory&#39;, function(target) {

          expect(target).toBeDefined();

        }
      ]);
    })

N.B. I know that `$controller` allows this for controllers, but I don&#39;t see an equivalent for factories.


Unit testing AngularJS factories that have dependencies

I&#39;m new to Karma, but I&#39;m wondering how to view its output in a browser (much like the way one interacts with Jasmine, when a runner.html file is present).

I watched the introductory screencast and I understand how to view test outputs in a console window, but in my browser, I get almost no content for Karma except

&gt; Karma - connected

Please advise!  I would like to avoid having to maintain a separate runner.html file, since the Karma configuration file already requires me to include all necessary script links.

View Karma Test Output in a Browser?

We have a pattern for resolving promises in our Angular app that has served us well up until Angular 1.6.0:

        resource.get().$promise
            .then(function (response) {
            // do something with the response
            }, function (error) {
                // pass the error the the error service
                return errorService.handleError(error);
            });

And here is how we are triggering the error in Karma:

        resourceMock.get = function () {
            var deferred = $q.defer();
            deferred.reject(error);
            return { $promise: deferred.promise };
        };

Now, with the update to 1.6.0, Angular is suddenly complaining in our unit tests (in Karma) for rejected promises with a &quot;Possibly unhandled rejection&quot; error. But we are handling the rejection in the second function that calls our error service.

What exactly is Angular looking for here? How does it want us to &quot;handle&quot; the rejection? 

Angular 1.6.0: &quot;Possibly unhandled rejection&quot; error

Using: 

`ng test`

Angular CLI runs the tests by default in Chrome, which is great, but what if I need to run them in a console-only environment (headless browser)?

Also it would be nice if I can specify if I want browser-less or not each time I run it, so something like:

`ng test --browsers MyHeadLessBrowser`

----------


**Edit**:

running PhantomJS I got the following:

&gt; PhantomJS 2.1.1 (Linux 0.0.0) ERROR
  TypeError: useValue,useFactory,data is not iterable!
  at http://localhost:9876/_karma_webpack_/polyfills.bundle.js:854


----------


&gt; eferenceError: Can&#39;t find variable: Intl in http://localhost:9876/_karma_webpack_/vendor.bundle.js (line 49362)
        intlDateFormat@http://localhost:9876/_karma_webpack_/vendor.bundle.js:49362:20


How can I run tests with a headless browser?

I&#39;m attempting to unit test controller code inside a module that takes other modules as dependencies, but haven&#39;t been able to figure out how to mock them properly. 

I&#39;m using the Jasmine Framework and running my tests with Karma (Testacular). 

**Module Code**

    var app = angular.module(&#39;events&#39;, [&#39;af.widgets&#39;, &#39;angular-table&#39;]);
    
    app.controller(&#39;eventsCtrl&#39;, function([dependencies]){
        $scope.events = [];
        ...
    });

    
**Spec Code**

    describe(&#39;events module&#39;, function(){
        var $scope,
            ctrl;

        beforeEach(function(){
            angular.mock.module(&#39;af.widgets&#39;, []);
            angular.mock.module(&#39;angular-table&#39;, []);
            module(&#39;events&#39;, [&#39;af.widgets&#39;, &#39;angular-table&#39;]);
        });

        beforeEach(inject(function($rootScope, $controller){
            $scope = $rootScope.new();
            ctrl = $controller(&#39;NameCtrl&#39;, {
                $scope: $scope,
            });
        }));

        it(&#39;should have an empty events array&#39;, function(){
            expect($scope.events).toBe([]);
        })
    });


The error I&#39;m getting is Karma is &quot;no module af.widgets&quot;, so obviously I&#39;m not mocking the module dependencies right. Any hints? 



    

Mocking AngularJS module dependencies in Jasmine unit tests

I used node.js to install karma. My first try failed when running the following command on Terminal: 

    npm install -g karma

That failed so I decided to use: 

    sudo npm install -g karma

After entering my password it seemed to install correctly. 
I am pasting part of the output of the install, maybe it will mean something to someone and it will be relevant to my question. After all the npm http messages this is what I see:

    &gt; ws@0.4.27 install /usr/local/share/npm/lib/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
    &gt; (node-gyp rebuild 2&gt; builderror.log) || (exit 0)
    
      CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
      SOLINK_MODULE(target) Release/bufferutil.node
      SOLINK_MODULE(target) Release/bufferutil.node: Finished
      CXX(target) Release/obj.target/validation/src/validation.o
      SOLINK_MODULE(target) Release/validation.node
      SOLINK_MODULE(target) Release/validation.node: Finished
    /usr/local/share/npm/bin/karma -&gt; /usr/local/share/npm/lib/node_modules/karma/bin/karma
    karma@0.8.6 /usr/local/share/npm/lib/node_modules/karma
    ├── pause@0.0.1
    ├── dateformat@1.0.2-1.2.3
    ├── xmlbuilder@0.4.2
    ├── colors@0.6.0-1
    ├── chokidar@0.6.2
    ├── growly@1.1.1
    ├── mime@1.2.9
    ├── q@0.9.6
    ├── rimraf@2.1.4 (graceful-fs@1.2.3)
    ├── coffee-script@1.6.3
    ├── minimatch@0.2.12 (sigmund@1.0.0, lru-cache@2.3.0)
    ├── optimist@0.3.5 (wordwrap@0.0.2)
    ├── glob@3.1.21 (inherits@1.0.0, graceful-fs@1.2.3)
    ├── LiveScript@1.0.1 (prelude-ls@1.0.1)
    ├── log4js@0.6.6 (dequeue@1.0.3, semver@1.1.4, async@0.1.15, readable-stream@1.0.2)
    ├── lodash@1.1.1
    ├── http-proxy@0.10.3 (pkginfo@0.2.3, utile@0.1.7)
    ├── istanbul@0.1.22 (abbrev@1.0.4, which@1.0.5, fileset@0.1.5, nopt@2.0.0, wordwrap@0.0.2, async@0.1.22, mkdirp@0.3.5, esprima@0.9.9, escodegen@0.0.24, handlebars@1.0.12)
    └── socket.io@0.9.16 (base64id@0.1.0, policyfile@0.0.4, redis@0.7.3, socket.io-client@0.9.16)

Then when I try to run the following command to create a karma config file with this command:

    karma init karma.config.js

this is the message that gets returned:

    -bash: karma: command not found

I have tried the same command with sudo before it but I get the same result.

Does anyone have any idea as to what is going on?
Any help is appreciated.

*Update!
I decided to check a file named: builderror.log
located in: /usr/local/share/npm/lib/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws

This is what it shows:

    gyp WARN EACCES user &quot;root&quot; does not have permission to access the dev dir &quot;/Users/eperez/.node-gyp/0.10.5&quot;
    gyp WARN EACCES attempting to reinstall using temporary dev dir &quot;/usr/local/share/npm/lib/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/.node-gyp&quot;
    gyp http GET http://nodejs.org/dist/v0.10.5/node-v0.10.5.tar.gz
    gyp http 200 http://nodejs.org/dist/v0.10.5/node-v0.10.5.tar.gz



karma command not found when karma already installed

I have two TypeScript packages, and one package (Package A) depends on the other (Package B). Each package has a unit test set up using Karma. When I run unit tests for each individually after installing all dependencies from NPM, the unit tests run fine. However, if I use `npm link package-b` in Package A and run Package A&#39;s unit tests then, I get the error stated in the title: &quot;TS2322: Type &#39;Timeout&#39; is not assignable to type &#39;number&#39;.&quot;

The line in question is a call to `setTimeout`. After digging, I found that while running the tests separately without `npm link`, TypeScript correctly identifies the `setTimeout` signature in `typescript/lib/lib.dom` as the desired type, but in the failing case after using `npm link` it is using using Node&#39;s `setTimeout` signature in `@types/node/index`. I confirmed this by changing the return type on `setTimeout` to `string` and observing the same error with `string` in the place of `Timeout`.

What I am not certain of is _why_ the TypeScript compiler has decided to use the alternative definition in this specific case, nor how I can convince it to use the desired definition. I am happy to post some code, but I am not sure what would be useful in this case given all that is on the failing line is the `setTimeout` call.

&quot;TS2322: Type &#39;Timeout&#39; is not assignable to type &#39;number&#39;&quot; when running unit tests

In Vojta Jina&#39;s excellent repository where he demonstrates testing of directives, he defines the directive controller outside of the module wrapper. See here:
https://github.com/vojtajina/ng-directive-testing/blob/master/js/tabs.js

Isn&#39;t that bad practice and pollute the global namespace?

If one were to have another place where it might be logical to call something TabsController, wouldn&#39;t that break stuff?

The tests for the mentioned directive is to be found here: https://github.com/vojtajina/ng-directive-testing/commit/test-controller

Is it possible to test directive controllers separate from the rest of the directive, without placing the controller in a global namespace?

It would be nice to encapsulate the whole directive within the app.directive(...) definition.

Unit-testing directive controllers in Angular without making controller global

I am trying to run karma tests from gulp task and I am getting this error:

    Error: 1
       at formatError (C:\Users\Tim\AppData\Roaming\npm\node_modules\gulp\bin\gulp.js:161:10)
       at Gulp.&lt;anonymous&gt; (C:\Users\Tim\AppData\Roaming\npm\node_modules\gulp\bin\gulp.js:187:15)
       at Gulp.emit (events.js:95:17)
       at Gulp.Orchestrator._emitTaskDone (C:\path\to\project\node_modules\gulp\node_modules\orchestrator\index.js:264:8)
       at C:\path\to\project\node_modules\gulp\node_modules\orchestrator\index.js:275:23
       at finish (C:\path\to\project\node_modules\gulp\node_modules\orchestrator\lib\runTask.js:21:8)
       at cb (C:\path\to\project\node_modules\gulp\node_modules\orchestrator\lib\runTask.js:29:3)
       at removeAllListeners (C:\path\to\project\node_modules\karma\lib\server.js:216:7)
       at Server.&lt;anonymous&gt; (C:\path\to\project\node_modules\karma\lib\server.js:227:9)
       at Server.g (events.js:180:16)

My system is `Windows 7`, nodejs version is `v0.10.32`, gulp version:

    [10:26:52] CLI version 3.8.8
    [10:26:52] Local version 3.8.9

Also, the same error I am getting on `Ubuntu 12.04 LTS` while on newer Ubuntu (not sure what version) and mac os it is seems to be working ok. What can cause this error?

**Update 5/11/2016**: Before writing comment about the fact that accepted answer hide errors, please, see first two comments to that particular accepted answer. Use it only if know what you are doing. Related info: https://github.com/karma-runner/gulp-karma/pull/15

Issue running karma task from gulp

When running my unit tests, from time to time, even if they pass, at the end of all the tests running, I will get the following error.

On my Jenkins CI build running PhantomJS:

    .PhantomJS 2.1.1 (Linux 0.0.0) ERROR
      {
        &quot;message&quot;: &quot;An error was thrown in afterAll\nReferenceError: Can&#39;t find variable: $ thrown&quot;,
        &quot;str&quot;: &quot;An error was thrown in afterAll\nReferenceError: Can&#39;t find variable: $ thrown&quot;
      }

Or on Chrome:

    Chrome 67.0.3396 (Windows 7 0.0.0) ERROR
      {
        &quot;message&quot;: &quot;An error was thrown in afterAll\n[object ErrorEvent] thrown&quot;,
        &quot;str&quot;: &quot;An error was thrown in afterAll\n[object ErrorEvent] thrown&quot;
      }

I also have really unreliable tests, without changing anything some times they would succeed and other times the same tests would fail, so I knew something weird was going on. 

Angular 6 Unit Tests: An error was thrown in afterAll\nReferenceError: Can&#39;t find variable: $ thrown

I have angular 2 webpack application, all webpack,karma configuration created as per angular.io webpack guide. 
I am not using aot.
I am writing jasmine unit test spec to test my components.
First I tried without async block, in that case , unit test just get execute only till fixture.detectChanges() call, code after that doesn&#39;t get executed. Seems like fixture.detectChanges call getting blocked infinitely.

I tried by including code in async block.
Then I get following error.
Error:Failed to execute &#39;send&#39; on &#39;XMLHttpRequest&#39; : Failed to load &#39;ng:///DynamicTestModule​/module.ngfactory.js&#39;

------
Code without async 

    beforeeach(()=&gt; {
    TestBed.configureTestingModule({
    imports:[],
    declaration :[Mycomp],
    providers:[{ provide:MyService, useclass:MyMockService}]
    });
     fixture=TestBed.createComponent(Mycomp);
     console.log(&#39; before detect changes&#39;):
     fixture.detectChanges():
     console.log(&#39;after detect changes&#39;);// this is not getting   
        logged .. karma shows 0 of 1 executed successfully

     });

--------
With async 

      beforeeach(async(()=&gt; {
     TestBed.configureTestingModule({
      imports:[],
      declaration :[Mycomp],
      providers:[{ provide:MyService,       useclass:MyMockService}]
      });
       fixture=TestBed.createComponent(Mycomp);
        fixture.detectChanges():
      }));

getting error Failed to load dynamictestmodule/module.ngfactory.js




Angular 2 unit testing - getting error Failed to load &#39;ng:///DynamicTestModule/module.ngfactory.js&#39;

I have run on my windows console:

    npm install -g yo grunt-cli bower
    
    npm install -g generator-angular
    
    yo angular

 

Then I started my project with webstorm and did right click on the karma.conf.js file in the project explorer where I have the menu item &#39;Run karma.conf.js&#39; and start the karma runner. Then I get his exception:

    ...\app\node_modules\karma\node_modules\di\lib\injector.js:9
          throw error(&#39;No provider for &quot;&#39; + name + &#39;&quot;!&#39;);
                ^
    Error: No provider for &quot;framework:jasmine&quot;! (Resolving: framework:jasmine)

Then in the console I read I can also use --force so I tried it: grunt --force

It took some time but there seemed to be no more errors. Heck why does --force install a provider ??? THIS was TESTED in the CMD.

grunt serve now worked and it started my browser with the starting app.

**So what was --force doing that the &#39;Error: No provider for &quot;framework:jasmine&quot;! (Resolving: framework:jasmine)&#39; is gone ?**

When I do grunt in the webstrom IDE I get again:

Warning: No provider for &quot;framework:jasmine&quot;! (Resolving: framework:jasmine) Use --force to continue.

So this problem is not solved.

Error: No provider for &quot;framework:jasmine&quot;! (Resolving: framework:jasmine)

I want to debug Karma tests in VS Code but I did not find out how. Is there any way to do that or will I have to use another IDE (WebStorm)?

How to debug Karma tests in Visual Studio Code?

I have an existing Angular/Laravel app in which Laravel acts as an API to the angular frontend serving only JSON data.  The page that loads the angular app, `index.php`, is currently served by Laravel. From there, Angular takes over. 

I&#39;m have a very difficult time trying to get started with Karma/Jasmine.  When running my tests using `karma start` or `karma start karma.conf.js` from the root directory of my project, I get the following error:

`ReferenceError: module is not defined`

Full output:

    INFO [karma]: Karma v0.12.28 server started at http://localhost:9876/
    INFO [launcher]: Starting browser Chrome
    WARN [watcher]: Pattern &quot;/Users/raph/coding/webroot/digitalocean/rugapp/public/rugapp/*.js&quot; does not match any file.
    INFO [Chrome 39.0.2171 (Mac OS X 10.9.5)]: Connected on socket 3OCUMp_xhrGtlGHwiosO with id 7897120
    Chrome 39.0.2171 (Mac OS X 10.9.5) hello world encountered a declaration exception FAILED
    	ReferenceError: module is not defined
    	    at Suite.&lt;anonymous&gt; (/Users/raph/coding/webroot/digitalocean/rugapp/tests/js/test.js:3:16)
    	    at jasmineInterface.describe (/Users/raph/coding/webroot/digitalocean/rugapp/node_modules/karma-jasmine/lib/boot.js:59:18)
    	    at /Users/raph/coding/webroot/digitalocean/rugapp/tests/js/test.js:1:1
    Chrome 39.0.2171 (Mac OS X 10.9.5): Executed 2 of 2 (1 FAILED) (0.005 secs / 0.003 secs)

However, the chrome broswer does launch with the following displayed:

![enter image description here][1]

My `karma.conf.js` file is as follows:

    // Karma configuration
    // Generated on Mon Dec 22 2014 18:13:09 GMT-0500 (EST)
    
    module.exports = function(config) {
      config.set({
    
        // base path that will be used to resolve all patterns (eg. files, exclude)
        basePath: &#39;public/rugapp/&#39;,
    
    
        // frameworks to use
        // available frameworks: https://npmjs.org/browse/keyword/karma-adapter
        frameworks: [&#39;jasmine&#39;],
    
    
        // list of files / patterns to load in the browser
        files: [
          &#39;*.html&#39;,
          &#39;**/*.js&#39;,
          &#39;../../tests/js/test.js&#39;,
          &#39;../../tests/js/angular/angular-mocks.js&#39;
        ],
    
    
        // list of files to exclude
        exclude: [
    
        ],
    
    
        // preprocess matching files before serving them to the browser
        // available preprocessors: https://npmjs.org/browse/keyword/karma-preprocessor
        preprocessors: {
        },
    
    
        // test results reporter to use
        // possible values: &#39;dots&#39;, &#39;progress&#39;
        // available reporters: https://npmjs.org/browse/keyword/karma-reporter
        reporters: [&#39;progress&#39;],
    
    
        // web server port
        port: 9876,
    
    
        // enable / disable colors in the output (reporters and logs)
        colors: true,
    
    
        // level of logging
        // possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
        logLevel: config.LOG_INFO,
    
    
        // enable / disable watching file and executing tests whenever any file changes
        autoWatch: true,
    
    
        // start these browsers
        // available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
        browsers: [&#39;Chrome&#39;],
    
    
        // Continuous Integration mode
        // if true, Karma captures browsers, runs the tests and exits
        singleRun: false
      });
    };



My `package.json` file is shown below:

    {
      &quot;devDependencies&quot;: {
        &quot;gulp&quot;: &quot;^3.8.8&quot;,
        &quot;karma&quot;: &quot;^0.12.28&quot;,
        &quot;karma-chrome-launcher&quot;: &quot;^0.1.7&quot;,
        &quot;karma-jasmine&quot;: &quot;^0.3.2&quot;,
        &quot;laravel-elixir&quot;: &quot;*&quot;
      }
    }


`test.js`

    describe(&quot;hello world&quot;, function() {
        var CreateInvoiceController;
        beforeEach(module(&quot;MobileAngularUiExamples&quot;));
        beforeEach(inject(function($controller) {
            CreateInvoiceController = $controller(&quot;CreateInvoiceController&quot;);
        }));
    
        describe(&quot;CreateInvoiceController&quot;, function() {
            it(&quot;Should say hello&quot;, function() {
                expect(CreateInvoiceController.message).toBe(&quot;Hello&quot;);
            });
        });
    });
    
    describe(&quot;true&quot;, function() {
        it(&quot;Should be true&quot;, function() {
            expect(true).toBeTruthy();
        });
    });

Any help would be *greatly* appreciated.


  [1]: http://i.stack.imgur.com/a1pD5.jpg

ReferenceError: module is not defined - Karma/Jasmine configuration with Angular/Laravel app

I&#39;m testing a component which subscribe router params. Every test pass and everything works fine. But if I look in the console, I can see an error:


&gt; Error during cleanup of component ApplicationViewComponent
&gt; localConsole.(anonymous function) @ context.js:232

Do you know why this occurs?

**I tried removing the `unsubscribe()` from `ngOnDestroy()` method and the error disappears.**

**Is karma/jasmine supporting `unsubscribe()` automatically?**

Here is the component and tests

## Component

    import { Component, OnInit } from &#39;@angular/core&#39;;   
    import { ActivatedRoute } from &#39;@angular/router&#39;;
    import { Subscription } from &#39;rxjs/Rx&#39;
    
    import { AppService } from &#39;app.service&#39;;
    
    @Component({
      selector: &#39;app-component&#39;,
      templateUrl: &#39;./app.component.html&#39;,
      styleUrls: [&#39;./app.component.scss&#39;]
    })
    export class AppComponent implements OnInit {
      private routeSubscription: Subscription;
    
      // Main ID
      public applicationId: string;
     
    
      constructor(
        private route: ActivatedRoute,
    	private _service: AppService
      ) { }
    
      ngOnInit() {
        this.routeSubscription = this.route.params.subscribe(params =&gt; {
          this.applicationId = params[&#39;id&#39;];
    
          this.getDetails();
          this.getList();
        });
      }
    
      getDetails() {
        this._service.getDetails(this.applicationId).subscribe(
          result =&gt; {     
            console.log(result);
          },
          error =&gt; {  
            console.error(error);        
          },
          () =&gt; {
            console.info(&#39;complete&#39;);
          }
        );
      }
    
      getList(notifyWhenComplete = false) {
        this._service.getList(this.applicationId).subscribe(
          result =&gt; {     
            console.log(result);
          },
          error =&gt; {  
            console.error(error);        
          },
          () =&gt; {
            console.info(&#39;complete&#39;);
          }
        );
      }
    
      ngOnDestroy() {
        this.routeSubscription.unsubscribe();
      }
    
    }

## Component spec file

    import { NO_ERRORS_SCHEMA } from &#39;@angular/core&#39;;
    import {
      async,
      fakeAsync,
      ComponentFixture,
      TestBed,
      tick,
      inject
    } from &#39;@angular/core/testing&#39;;
    import {
      RouterTestingModule
    } from &#39;@angular/router/testing&#39;;
    import {
      HttpModule
    } from &#39;@angular/http&#39;;
    import { Observable } from &#39;rxjs/Observable&#39;;
    import { Router, ActivatedRoute } from &#39;@angular/router&#39;;
    
    // Components
    import { AppComponent } from &#39;./app.component&#39;;
    
    // Service
    import { AppService } from &#39;app.service&#39;;
    import { AppServiceStub } from &#39;./app.service.stub&#39;;
    
    let comp:    AppComponent;
    let fixture: ComponentFixture&lt;AppComponent&gt;;
    let service: AppService;
    
    let expectedApplicationId = &#39;abc123&#39;;
    
    describe(&#39;AppComponent&#39;, () =&gt; {
      beforeEach(async(() =&gt; {
        TestBed.configureTestingModule({
          declarations: [AppComponent],
          imports: [RouterTestingModule, HttpModule],
          providers: [
            FormBuilder,
            {
              provide: ActivatedRoute,
              useValue: {
                params:  Observable.of({id: expectedApplicationId})
              }
            },
            {
              provide: AppService,
              useClass: AppServiceStub
            }    
          ],
          schemas: [ NO_ERRORS_SCHEMA ]
        })
        .compileComponents();
      }));
    
      tests();
    });
    
    function tests() {
      beforeEach(() =&gt; {
        fixture = TestBed.createComponent(AppComponent);
        comp = fixture.componentInstance;
    
        service = TestBed.get(AppService);
      });
    
    
      /*
      *   COMPONENT BEFORE INIT
      */
      it(`should be initialized`, () =&gt; {
        expect(fixture).toBeDefined();
        expect(comp).toBeDefined();
      });
    
    
      /*
      *   COMPONENT INIT
      */
    
      it(`should retrieve param id from ActivatedRoute`, async(() =&gt; {
        fixture.detectChanges();
    
        expect(comp.applicationId).toEqual(expectedApplicationId);
      }));
    
      it(`should get the details after ngOnInit`, async(() =&gt; {
        spyOn(comp, &#39;getDetails&#39;);
        fixture.detectChanges();
    	
    	expect(comp.getDetails).toHaveBeenCalled();
      }));
    
      it(`should get the list after ngOnInit`, async(() =&gt; {
        spyOn(comp, &#39;getList&#39;);
        fixture.detectChanges();
    	
    	expect(comp.getList).toHaveBeenCalled();
      }));
    }

### service.stub

    import { Observable } from &#39;rxjs/Observable&#39;;
    
    export class AppServiceStub {
      getList(id: string) {
        return Observable.from([              
    	  {
    		id: &quot;7a0c6610-f59b-4cd7-b649-1ea3cf72347f&quot;,
    		name: &quot;item 1&quot;
    	  },
    	  {
    		id: &quot;f0354c29-810e-43d8-8083-0712d1c412a3&quot;,
    		name: &quot;item 2&quot;
    	  },
    	  {
    		id: &quot;2494f506-009a-4af8-8ca5-f6e6ba1824cb&quot;,
    		name: &quot;item 3&quot;		
    	  }
        ]);
      }
      getDetails(id: string) {
        return Observable.from([      
          {        
            id: id,
            name: &quot;detailed item 1&quot;         
          }
        ]);
      }
    }

Testing Angular component with unsubscribe Error during cleanup of component

I am looking at karma&#39;s reporter configuration.

There are some possible reporters: progress, dots, growl, coverage. I don&#39;t find any detailed information explaining each of the options.

I tried progress and dots, they all print log to console, the result looks the same. What are the differences between them?

Growl, coverage need a little more configuration, so I didn&#39;t succeed testing them.

What are the differences between karma reporters?

Trying to get karma working with requirejs. I don&#39;t understand why I am getting all of these errors when running Karma:

    ERROR: &#39;There is no timestamp for /base/test/mainSpec.js?bust=1387739317116!&#39;
    ERROR: &#39;There is no timestamp for /base/app/main.js?bust=1387739317116!&#39;
    ERROR: &#39;There is no timestamp for /base/bower_components/jquery/jquery.js?bust=1387739317116!&#39;

When I go to the network tab in inspector, all of the files are there with no 404s.

I&#39;m a little confused because karma seems to be looking for a &#39;base&#39; directory but there is no &#39;base&#39; directory in my project. According to the karma docs:

&gt; Karma serves files under the /base directory. So, on the server
&gt; requests to files will be served up under
&gt; `http://localhost:9876/base/*`. The Require.js config for baseUrl gives
&gt; a starting context for modules that load with relative paths. When
&gt; setting this value for the Karma server it will need to start with
&gt; /base. We want the baseUrl for our tests to be the same folder as the
&gt; base url we have in src/main.js, so that relative requires in the
&gt; source won’t need to change. So, as we want our base url to be at
&gt; src/, we need to write /base/src.

This confusing to say the least. Am I supposed to have a baseUrl configuration in my main.js file that points to &#39;/base&#39;?

karma error &#39;There is no timestamp for&#39;

I&#39;m trying to run Karma/Jasmine from Grunt on a project generated with 
http://newtriks.com/2013/12/31/automating-react-with-yeoman-and-grunt/

Karma launches PhantomJS (or Chrome) and, depending on singleRun, it either times out or just sits there and does nothing. I&#39;ve tried changing `captureTimeout` and `browserNoActivityTimeout` based on reading solutions from people with similar problems, but it doesn&#39;t seem to work.

My relevant pacakge versions etc.:

 - NodeJS: 0.10.25
 - Karma: 0.12.16
 - Webpack: 1.1.11
 - webpack-dev-server: 1.4.1
 - karma-jasmine: 0.1.5
 - Linux: Ubuntu 14.04

I&#39;ve found [someone with the same problem][1] on OS X: 

I&#39;ve tried updating all my dev dependencies to the latest versions but the problem still remains.

My console output is below. The webpack lines referring to _bundle is now VALID/INVALID_ are worrying, but I can&#39;t find any info on what they mean. Here&#39;s my console output:

    Running &quot;karma:unit&quot; (karma) task
    DEBUG [config]: autoWatch set to false, because of singleRun
    DEBUG [plugin]: Loading karma-* from /home/ed/workspace/wwb-app/node_modules
    DEBUG [plugin]: Loading plugin /home/ed/workspace/wwb-app/node_modules/karma-chrome-launcher.
    DEBUG [plugin]: Loading plugin /home/ed/workspace/wwb-app/node_modules/karma-coffee-preprocessor.
    DEBUG [plugin]: Loading plugin /home/ed/workspace/wwb-app/node_modules/karma-firefox-launcher.
    DEBUG [plugin]: Loading plugin /home/ed/workspace/wwb-app/node_modules/karma-html2js-preprocessor.
    DEBUG [plugin]: Loading plugin /home/ed/workspace/wwb-app/node_modules/karma-jasmine.
    DEBUG [plugin]: Loading plugin /home/ed/workspace/wwb-app/node_modules/karma-phantomjs-launcher.
    DEBUG [plugin]: Loading plugin /home/ed/workspace/wwb-app/node_modules/karma-requirejs.
    DEBUG [plugin]: Loading plugin /home/ed/workspace/wwb-app/node_modules/karma-script-launcher.
    DEBG [plugin]: Loading plugin /home/ed/workspace/wwb-app/node_modules/karma-webpack-plugin.
    INFO [karma]: Karma v0.12.16 server started at  http://localhost:8080/
    INFO [launcher]: Starting browser PhantomJS
    DEBUG [temp-dir]: Creating temp dir at /tmp/karma-98204612
    DEBUG [launcher]: /home/ed/workspace/wwb-app/node_modules/karma-phantomjs-launcher/node_modules/phantomjs/lib/phantom/bin/phantomjs /tmp/karma-98204612/capture.js
    Hash: 89285186567c1bc5bb7f
    Version: webpack 1.1.11
    Time: 2ms
    Asset  Size  Chunks       Chunk Names
    webpack: bundle is now VALID.
    webpack: bundle is now INVALID.
    DEBUG [web-server]: serving: /home/ed/workspace/wwb-app/node_modules/karma/static/client.html
    DEBUG [web-server]: serving: /home/ed/workspace/wwb-app/node_modules/karma/static/karma.js
    DEBUG [web-server]: upgrade /socket.io/1/websocket/CjC8pnQq5It2z_kWYB98
    DEBUG [karma]: A browser has connected on socket CjC8pnQq5It2z_kWYB98
    INFO [PhantomJS 1.9.7 (Linux)]: Connected on socket CjC8pnQq5It2z_kWYB98 with id 98204612
    DEBUG [launcher]: PhantomJS (id 98204612) captured in 1.704 secs
    WARN [PhantomJS 1.9.7 (Linux)]: Disconnected (1 times), because no message in 30000 ms.
    
    DEBUG [karma]: Run complete, exitting.
    DEBUG [launcher]: Disconnecting all browsers
    DEBUG [launcher]: Process PhantomJS exited with code 0
    DEBUG [temp-dir]: Cleaning temp dir /tmp/karma-98204612
    Warning: Task &quot;karma:unit&quot; failed. Use --force to continue.
    
    Aborted due to warnings.

Here&#39;s my `karma.conf.js` file:

    &#39;use strict&#39;;
    
    module.exports = function (config) {
    config.set({
        basePath: &#39;&#39;,
        frameworks: [&#39;jasmine&#39;],
        files: [
            &#39;test/helpers/**/*.js&#39;,
            &#39;test/spec/components/**/*.js&#39;
        ],
        preprocessors: {
            &#39;test/spec/components/**/*.js&#39;: [&#39;webpack&#39;]
        },
        webpack: {
            cache: true,
            module: {
                loaders: [{
                    test: /\.css$/,
                    loader: &#39;style!css&#39;
                }, {
                    test: /\.gif/,
                    loader: &#39;url-loader?limit=10000&amp;minetype=image/gif&#39;
                }, {
                    test: /\.jpg/,
                    loader: &#39;url-loader?limit=10000&amp;minetype=image/jpg&#39;
                }, {
                    test: /\.png/,
                    loader: &#39;url-loader?limit=10000&amp;minetype=image/png&#39;
                }, {
                    test: /\.js$/,
                    loader: &#39;jsx-loader&#39;
                }]
            }
        },
        webpackServer: {
            stats: {
                colors: true
            }
        },
        exclude: [],
        port: 8080,
        logLevel: config.LOG_DEBUG,
        colors: true,
        autoWatch: true,
        // Start these browsers, currently available:
        // - Chrome
        // - ChromeCanary
        // - Firefox
        // - Opera
        // - Safari (only Mac)
        // - PhantomJS
        // - IE (only Windows)
        browsers: [&#39;PhantomJS&#39;],
        reporters: [&#39;progress&#39;],
        captureTimeout: 60000,
        browserNoActivityTimeout: 60000,
        singleRun: true
    });
    };


  [1]: https://stackoverflow.com/questions/23667102/disconnected-1-times-because-no-message-in-10000-ms-using-karma-jasmine

Karma/Jasmine times out without running tests

I&#39;m testing service A, but service A depends on service B (i.e. service B is injected into service A).

I&#39;ve seen [this question][1] but my case is a bit different because in my opinion it makes more sense to *mock* service B instead of injecting an actual instance of service B.  I&#39;d mock it with a jasmine spy.

Here&#39;s a sample test:

    describe(&quot;Sample Test Suite&quot;, function() {

      beforeEach(function() {

        module(&#39;moduleThatContainsServiceA&#39;);

        inject([
          &#39;serviceA&#39;, function(service) {
            this.service = service;
          }
        ]);

      });

      it(&#39;can create an instance of the service&#39;, function() {
        expect(this.service).toBeDefined();
      });
    });

The error I get is:

&gt; Error: Unknown provider: serviceBProvider

How could I do something like this?

  [1]: https://stackoverflow.com/q/10551986/295797

Injecting dependent services when unit testing AngularJS services

I have some simple karma / jasmine unit-tests that run against an angularjs app. I use the latest version of Chrome and run my tests from within the WebStorm IDE.

Sometimes the test suite runs very quickly (0.24 seconds)

Sometimes exactly the same test suite against exactly the same code runs very slowly (120 seconds)

I have tried every common sense fix. I have scoured the web to try and discover what I am doing wrong.

Why do my tests run so slowly?

Why are my AngularJS, Karma / Jasmine tests running so slowly?

Hi have some error with testing my App made with Angular 7. I do not have much experience in angular, so I would need your help+


    Error: StaticInjectorError(DynamicTestModule)[BeerDetailsComponent -&gt; ActivatedRoute]: 
      StaticInjectorError(Platform: core)[BeerDetailsComponent -&gt; ActivatedRoute]: 
        NullInjectorError: No provider for ActivatedRoute!

the testing code is like this:


    import { async, ComponentFixture, TestBed, inject } from &#39;@angular/core/testing&#39;;
    import { BeerDetailsComponent } from &#39;./beer-details.component&#39;;
    import {
      HttpClientTestingModule,
      HttpTestingController
    } from &#39;@angular/common/http/testing&#39;;
    
    describe(&#39;BeerDetailsComponent&#39;, () =&gt; {
      let component: BeerDetailsComponent;
      let fixture: ComponentFixture&lt;BeerDetailsComponent&gt;;
    
      beforeEach(async(() =&gt; {
        TestBed.configureTestingModule({
          imports: [HttpClientTestingModule],
          declarations: [ BeerDetailsComponent ]
        })
        .compileComponents();
      }));
    
      beforeEach(() =&gt; {
        fixture = TestBed.createComponent(BeerDetailsComponent);
        component = fixture.componentInstance;
        fixture.detectChanges();
      });
    
      it(&#39;should create&#39;,
      inject(
        [HttpTestingController],
        () =&gt; {
          expect(component).toBeTruthy();
        }
      )
    )
    });

I really can&#39;t find any solution.

Daniele



Angular 7 Test: NullInjectorError: No provider for ActivatedRoute

I just started with unit test my angular app with karma. Everything working as expected

&gt; Chrome 26.0 (Windows): Executed 1 of 1  
&gt; Chrome 26.0 (Windows): Executed 1 of 1 SUCCESS (0.878 secs / 0.112 secs)

However, is there any way to output more info about the result of the test. For example, Suite and test names it is executing and their result. I&#39;ve read few tutorials where Jasmine test result outputs in browser. I&#39;m wondering it can be achieved in karma too.

karma test runner detailed test report in console

I am trying to figure out the best way to debug my unit tests when I break them. Typically in previous test environments I could just run the tests in the browser and breakpoint the test, or the code and see why my test was failing. I can&#39;t seem to figure out how to do that with testacular. Is there an easy way to debug unit tests?

debug in browser using testacular (now karma)

When I run karma on my webapp, I only get generic messages like tests passed - is there a way to get a list of passing tests? How do I get more verbose output? 

I cannot find this anywhere in the documentation.

All Karma Runner Solutions on Gang of Coders

Total of 40 Karma Runner Solutions