问题
How would I go ahead with running a jasmine test for the following component:
@Component({
moduleId: module.id,
selector: "testComp",
template: "<div>{{value}}</div>",
})
export class TestComp {
public value: string = "This is me";
constructor(public zone: NgZone) {
this.zone.run(() => console.log("zone is here"));
}
}
The following fails with the Can't resolve all parameters for NgZone:
describe("test", () => {
let fixture;
let component;
beforeEach(async(() => {
TestBed.configureTestingModule({
declarations: [TestComp],
schemas: [NO_ERRORS_SCHEMA],
providers: [NgZone]
}).compileComponents;
}));
beforeEach(() => {
fixture = TestBed.createComponent(TestComp);
component = fixture.debugElement.componentInstance;
});
it("should check that the component is created", () => {
expect(component).toBeTruthy();
});
})
using Angular 4.1.3. I found the MockNgZone class @ https://no-shadow-angular-io.firebaseapp.com/docs/ts/latest/api/core/testing/MockNgZone-class.html. But it seems unavailable in the @angular/core/testing for this particular version:
Anybody knows what I should do to test this component?
Regards
回答1:
If your problem is about runOutsideAngular
because then you cannot use async
or fakeAsync
, the only thing you need to mock is that function and the following works well:
const ngZone = TestBed.get(NgZone);
spyOn(ngZone, 'runOutsideAngular').and.callFake((fn: Function) => fn());
回答2:
It's a bit of a mystery, MockNgZone is still in the source but removed from the public API.
Given the simple implementation of mock run()
export class MockNgZone extends NgZone {
...
run(fn: Function): any { return fn(); }
I would use this to get you over the hump
const mockNgZone = jasmine.createSpyObj('mockNgZone', ['run', 'runOutsideAngular']);
mockNgZone.run.and.callFake(fn => fn());
TestBed.configureTestingModule({
...
providers: [
{ provide: NgZone, useValue: mockNgZone },
]
回答3:
In Angular 5.2.4 (installed via Angular CLI 1.6.8) the mock was removed from the codebase so there's no need to use it in Jasmine. Just skip the declaration of NgZone in providers list.
回答4:
We had the same issue, exactly. At the end we left ngZone as is, and make sure we test the callbacks it uses.
beforeEach(async(() => {
TestBed.configureTestingModule({
...
providers: [NgZone]
})
}));
And for code that used the ngZone such as
zone.run(someFunction)
We made sure to have good test coverage someFunction
with unit tests.
来源:https://stackoverflow.com/questions/47503064/running-jasmine-tests-for-a-component-with-ngzone-dependency