You want to inject a fake ActivatedRoute to your component, since you create it yourself in the test, and the router thus doesn’t create it for you and inject an ActivatedRoute. So you can use something like this: describe(‘SomeComponent’, () => { const fakeActivatedRoute = { snapshot: { data: { … } } } as … Read more
import { TestBed } from ‘@angular/core/testing’; import { HttpClientTestingModule, HttpTestingController } from ‘@angular/common/http/testing’; import {HttpClientModule} from ‘@angular/common/http’; import { myService } from ‘./myservice’; describe(‘myService’, () => { beforeEach(() => TestBed.configureTestingModule({ imports: [HttpClientTestingModule], providers: [myService] })); it(‘should be created’, () => { const service: myService = TestBed.get(myService); expect(service).toBeTruthy(); }); it(‘should have getData function’, () => { … Read more
toThrow matcher requires function to be passed as argument to expect so you can simply wrap your function call in anonymous function: expect(function() { myFunc(arg1, arg2, arg3); }).not.toThrow(); You can also use bind to create new ‘version’ of your function that when called will be passed provided arguments: expect(myFunc.bind(null, arg1, arg2, arg3)).not.toThrow();
Testing mat-dialogs can be tricky. I tend to use a spy object for the return from a dialog open (dialogRefSpyObj below) so I can more easily track and control tests. In your case it might look something like the following: describe(‘ModalService’, () => { let modalService: ModalService; let dialogSpy: jasmine.Spy; let dialogRefSpyObj = jasmine.createSpyObj({ afterClosed … Read more
This worked for me nx test –test-file example.spec.ts
Fixed by installing the karma-spec-reporter npm install karma-spec-reporter –save-dev and adding this my karma.config.js reporters: [‘spec’], According to karma documentation By default, Karma loads all NPM modules that are siblings to it and their name matches karma-*. but some users have had to add the following to their config plugins: [‘karma-spec-reporter’]
You need to inject $rootScope in your test and trigger $digest on it.
toContain() now can actually be used for substring in string checks: expect(view.$el.html()).toContain(‘Admin’);
You are on the good road to understand all of it. Ng test (Jasmine + Angular Testing Utilities tests launched through Karma): You are using the jasmine framework to write your tests and define them as suites and expect results that you can test, but the main thing is that you are actually using the … Read more
You need to add your second component when creating your testing module as that module is part of component 1. If you don’t the module won’t have my-component2 and the input will be invalid. TestBed.configureTestingModule({ declarations: [ MyComponent1Component, MyComponent2Component ], imports: [], providers: [MyService1Service, HttpClient, HttpHandler, HttpTestingController] })