I seem to have fixed my problem, for anyone with a similar problem: Within my karma.conf.js I added the following: plugins: [ ‘karma-chrome-launcher’, ‘karma-jasmine’ ], At first I added ‘karma-jasmine’ but was then met with “Can not load “Chrome”, it is not registered!” This was solved by adding ‘karma-chrome-launcher’ as a plug-in Not sure if … Read more
Here’s a low-levelish way of doing it with jasmine, testing that pushState works as expected and that your router sets up things properly… I assume a router that has been initialized and has a home route mapped to ”. You can adapt this for your other routes. I also assume you’ve done in your app … Read more
You can try putting $rootScope.$apply() in an afterEach() callback function. Promises resolve on $apply() in Angular. afterEach(function(){ rootScope.$apply(); });
Ah, obvious now…I can access the vm variable through making a reference to the controller that’s created in the test: it(“should assign Dashboard as title”, function () { var vm = controller(“dashboard”, { $scope: scope }); expect(vm.title).toBe(“Dashboard”); });
The answer seems to be … expect(A.NONEXISTINGPROP).not.toBeDefined(); ie remove the name bit
spyOn(window, ‘alert’); . . . expect(window.alert).toHaveBeenCalledWith(‘a message’);
Update 2022; Use .withContext(…) method instead of below (as optional parameter is deprecated). Jasmine already supports optional parameter in all matchers (toBe, toContain, and others), so you can use: expect(true).toBe(false, ‘True should be false’). Then in output it will look like this: Message: Expected true to be false, ‘True should be false’. Link to commit … Read more
You say you tried importing the wildcard and spying on default? What was the issue with that approach? I just ran into this problem and doing this solved it for me: import * as widget from ‘./widget’; describe(‘widget spec’, () => { beforeEach(() => { spyOn(widget, ‘default’); }); });
since no one answered my question, so I’m pasting my code snippet for the reference to help people who might get this situation. sampleLoggedIn.guard.ts import {Injectable} from ‘@angular/core’; import {Router, CanActivate} from ‘@angular/router’; import {StorageService} from ‘../storage.service’; @Injectable() export class LoggedInGuard implements CanActivate { constructor(private router: Router, private storageService: StorageService) { } /**Overriding canActivate to … Read more
I had the same problem, just figured it out. Remove the line: {provide: Router, useValue: mockRouter} and it will work. The thing is when you import RouterTestingModule you should remove all router mocked providers, save for ActiveRoute, etc.