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.
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
Import MatMenuModule in your feature Module OR the Module where this component resides in. import { MatMenuModule} from ‘@angular/material/menu’; and imports: [ MatMenuModule ]
In my case the problem was that in my source code I had code directly setting the href on the location object, like window.location.href=”https://stackoverflow.com/questions/29352578/somewhere”; In my specs I set up a onbeforeunload listener that just returns a string instead of allowing the redirect to take place: beforeAll(() => { window.onbeforeunload = () => ‘Oh no!’; … Read more
Grunt –force works because you tell it to bypass the karma tests. Notice if you run grunt –force, it’ll still say “Done, but with warnings”. To fix: add “karma-jasmine” and “karma-chrome-launcher” (or whatever launcher you use) to the devDependencies in packages.json and run npm install again. npm install karma-jasmine –save-dev npm install karma-chrome-launcher –save-dev This … Read more
Update for Angular version 9 The source files have been moved but you can still debug this way if you do the following steps In devtools, select the sources tab Press CTRL + P Type in the name of the file you want to debug Valid for versions below 9 The other answers are completely … Read more
The “Error during component cleanup” error message happens because when ngOnDestroy() is called, this.routeSubscription is undefined. This happens because ngOnInit() was never invoked, meaning that you never subscribed to the route. As described in the Angular testing tutorial, the component isn’t initialized fully until you call fixture.detectChanges() the first time. Therefore, the correct solution is … Read more
I have faced with the similar problem. The solution was flush function usage. import { fakeAsync, flush } from ‘@angular/core/testing’; it(‘test something’, fakeAsync(() => { // … flush(); }));
You could do one of two things: 1: Actually wait in the test 250+1 ms in a setTimeout(), then check if the element actually disappeared. 2: use fakeAsync() and tick() to simulate time in the test – a tick() will resolve the setTimeout in the original close(), and the check could happen right after in … Read more
jasmine.createSpy can be used when there is no function to spy on. It will track calls and arguments like a spyOn but there is no implementation. jasmine.createSpyObj is used to create a mock that will spy on one or more methods. It returns an object that has a property for each string that is a … Read more