Try adding this code to your config. I had a similar issue once, and this workaround did the trick. app.config([‘$qProvider’, function ($qProvider) { $qProvider.errorOnUnhandledRejections(false); }]);
There are two ways to accomplish something like this that I know of: Use $provide and an anonymous module to inject the mock. Inject the service you would like to mock and use jasmine’s spying ability to provide mock values. The second option only works if you know exactly which methods your code under test … Read more
I’m using an angular setup with angular seed. I ended up solving this with straight .json fixture files and jasmine-jquery.js. Others had alluded to this answer, but it took me a while to get all the pieces in the right place. I hope this helps someone else. I have my json files in a folder … Read more
You don’t. Karma is only for testing browser-based code. If you have a project with mocha tests on the backend and karma/mocha on the front end, try editing your package.json under scripts to set test to: mocha -R spec && karma run karma.con Then, if npm test returns true, you’ll know it’s safe to commit … Read more
That is because you need to configurate karma to load then serve them when requested 😉 In your karma.conf.js file you should already have defined files and/or patterns like : // list of files / patterns to load in the browser files : [ {pattern: ‘app/lib/angular.js’, watched: true, included: true, served: true}, {pattern: ‘app/lib/angular-*.js’, watched: … Read more
This can be an error in the providers declarations. When you try to mock a provider and use useClass instead of useValue the error “TypeError: ctor is not a constructor” is fired. Here is an example that fires the error : providers: [{provide: OrderService, useClass: new OrderServiceMock()}] The correct declaration is : providers: [{provide: OrderService, … 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
You could try with using window.setTimeout instead of just setTimeout, this way the typescript one will be explicitly used
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
Not recommended by the current maintainer of Protractor: https://github.com/angular/protractor/issues/9#issuecomment-19927049 Protractor and Karma should not be used together; instead they provide separate systems for running tests. Protractor and Karma cover different aspects of testing – Karma is intended mostly for unit tests, while Protractor should be used for end to end testing. Protractor is built on … Read more