我有一个失败的异步角度组件dom测试,但它的同步等价物失败了,我不明白为什么。
这是茉莉花测试:
describe('Availability Component', () => {
let fixture: ComponentFixture<AvailabilityComponent>;
const absenceService = jasmine.createSpyObj('AbsenceService', ['findAbsences']);
absenceService.findAbsences.and.returnValue(of([{}]));
beforeEach(async(() => {
TestBed.configureTestingModule({
declarations: [AvailabilityComponent],
imports: [CalendarModule.forRoot()],
providers: [{provide: AbsenceService, useValue: absenceService}]
}).compileComponents();
}));
beforeEach(() => {
fixture = TestBed.createComponent(AvailabilityComponent);
});
const printAbsenceReasons = function () {
console.log(fixture.debugElement.queryAll(By.css('.calendarAbsence'))
.map(e => e.nativeElement.textContent)
.join(','));
};
it('should synchronously find absences in calendar view', () => {
fixture.detectChanges();
console.log('synchronous test');
printAbsenceReasons();
});
it('should asynchronously find absences in calendar view', fakeAsync(() => {
fixture.detectChanges();
tick();
fixture.detectChanges();
tick();
console.log('asynchronous test');
printAbsenceReasons();
}));
});
在同步情况下创建正确的输出,但在异步情况下创建错误的输出:
LOG: 'processing absences'
HeadlessChrome 0.0.0 (Mac OS X 10.13.4): Executed 0 of 51 SUCCESS (0 secs / 0 secs)
LOG: 'synchronous test'
HeadlessChrome 0.0.0 (Mac OS X 10.13.4): Executed 0 of 51 SUCCESS (0 secs / 0 secs)
LOG: 'A,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,'
HeadlessChrome 0.0.0 (Mac OS X 10.13.4): Executed 0 of 51 SUCCESS (0 secs / 0 secs)
ERROR: 'Spec 'Availability Component should synchronously find absences in calendar view' has no expectations.'
HeadlessChrome 0.0.0 (Mac OS X 10.13.4): Executed 0 of 51 SUCCESS (0 secs / 0 secs)
LOG: 'processing absences'
HeadlessChrome 0.0.0 (Mac OS X 10.13.4): Executed 1 of 51 SUCCESS (0 secs / 0 secs)
LOG: 'asynchronous test'
HeadlessChrome 0.0.0 (Mac OS X 10.13.4): Executed 1 of 51 SUCCESS (0 secs / 0 secs)
LOG: ''
HeadlessChrome 0.0.0 (Mac OS X 10.13.4): Executed 1 of 51 SUCCESS (0 secs / 0 secs)
ERROR: 'Spec 'Availability Component should asynchronously find absences in calendar view' has no expectations.'
我不确定这是否与我正在使用的angular-calendar组件有关,或者这是否是我的测试代码的一个更基本的问题。
以下是我的组件、模板和服务代码,以供参考:
@Component({
selector: 'app-availability',
templateUrl: './availability.component.html',
styleUrls: ['availability.component.scss']
})
export class AvailabilityComponent implements OnInit {
viewDate: Date = new Date();
absenceEvents: CalendarEvent[] = [];
constructor(private absenceService: AbsenceService) {
}
ngOnInit() {
this.getAbsences();
}
getAbsences() {
this.absenceService.findAbsences()
.subscribe(ignored => {
console.log('processing absences');
this.absenceEvents = [{
start: new Date(2018, 3, 29), title: 'A'
}];
});
}
getAbsence(events: CalendarEvent[]) {
return events[0] ? events[0].title : '';
}
}
模板代码:
<div>
<div>
<mwl-calendar-month-view
[viewDate]="viewDate"
[events]="absenceEvents"
[cellTemplate]="availabilityCellTemplate">
</mwl-calendar-month-view>
</div>
<ng-template #availabilityCellTemplate let-day="day">
<div class="calendarAbsence">{{ getAbsence(day.events) }}</div>
</ng-template>
</div>
服务代码:
@Injectable()
export class AbsenceService {
private url = environment.APP_SHIFT_SERVICE_BASE_URL + '/api/absences';
constructor(private http: HttpClient) {
}
findAbsences(): Observable<Absence[]> {
console.error('Actual findAbsences() called');
return this.http.get<Absence[]>(this.url);
}
}
最佳答案
不幸的是,这似乎与fakeasync专区有关,而与异步测试无关。
我设法让一个工作异步测试与async
而不是fakeAsync
一起工作:
it('should asynchronously find absences in calendar view', async(() => {
fixture.detectChanges();
fixture.whenStable().then(() => {
console.log('asynchronous test');
printAbsenceReasons(fixture);
expect(getAbsenceElements(fixture).length).toEqual(35);
});
});
}));
我调试了失败的
fakeAsync
和成功的同步测试。它们都调用库中的一个名为getMonthView
的方法“calendar utils”,该方法与“angular calendar”由同一作者编写:https://github.com/mattlewis92/calendar-utils/blob/master/src/calendar-utils.ts
在这个method中,日期参数和其他日期计算本身似乎都出错了。
我目前只能假设它与这个known issue in zone.js有关。我的角度是5.2,但我认为它还是相关的。无论如何,我确信我的测试代码基本上是正确的,但问题出在别处。