I'm trying to write a test for an angular service which has a Subject property and a method to call .next()
on that subject.
The service is the following:
@Injectable()
export class SubjectService {
serviceSubjectProperty$: Subject<any> = new Subject();
callNextOnSubject(data: any) {
this.serviceSubjectProperty$.next(data);
}
}
And the test file for that service:
import { TestBed, inject } from '@angular/core/testing';
import { SubjectService } from './subject.service';
describe('SubjectService', () => {
beforeEach(() => {
TestBed.configureTestingModule({
providers: [
SubjectService
]
});
});
it('callNextOnSubject() should emit data to serviceSubjectProperty$ Subject',
inject([SubjectService], (subjectService) => {
subjectService.callNextOnSubject('test');
subjectServiceProperty$.subscribe((message) => {
expect(message).toBe('test');
})
}));
});
The test always passes event if I change the argument of subjectService.callNextOnSubject
from 'test'
to anything else.
I have also tried wrapping everything with async
and fakeAsync
, but the result is the same.
What would be the correct way to test if callNextOnSubject
is emitting data to the serviceSubjectProperty$
Subject?
I found this article while searching for the solution:
http://www.syntaxsuccess.com/viewarticle/unit-testing-eventemitter-in-angular-2.0
and it worked well for me (it's very short, don't be afraid to open it).
I'm pasting it here so maybe it will help those which came to this site looking for answer.
Regarding the question asked - I think that you need to change:
subjectService.callNextOnSubject('test');
subjectServiceProperty$.subscribe((message) => {
expect(message).toBe('test');
})
to
subjectServiceProperty$.subscribe((message) => {
expect(message).toBe('test');
})
subjectService.callNextOnSubject('test');
, so subscribe at first, then emit an event.
If you emit 'test'
before subscription, then nothing will "catch" that event.