使用未触发订阅方法可观察到的角单元测试

Question

How can I get this subscribe to fire in my unit tests.

.close.then((resolve: IModelInstance): void => {
    resolve.status$.subscribe((status: Status): void => {
      this._checkStatus(status);
    });
  });

the this._checkStatus(status) has some logic that checks value in order to fire the component's output.

Now so far in my unit tests, I have mocked the promise to return a resolve callback like so:

......as Spy).and.returnValue({
  close: new Promise((resolve: Function): void => {
    closeResolve = resolve;
  })
});

The data to pass to closeResolve is a follows:

        beforeEach(async(() => {

          closeResponseSubject = new Subject<Status>();

          closeResponse = {} as Partial<Instance> as Instance;

          closeResponse.status$ = closeResponseSubject.asObservable();

          closeResponseSubject.next(Status.CREATED);

          closeResolve(closeResponse);
        }));

On using this appraoch, in the component the tests do go into the "then" but not into the susbcribe. I've looked at different questions and answers here but so far no luck. I just quite don't understand why the test won't go into the subscribe. I don't know

Answer 1

Failed to figure out why the subscribe never fires with this appraoch, so instead of doing this:

.close.then((resolve: IModelInstance): void => {
    resolve.status$.subscribe((status: Status): void => {
      this._checkStatus(status);
    });
  });

I used this implementation instead:

.close.then((resolve: IModelInstance): void => {
    this._checkStatus(resolve.status);
  });

Then in the unit test I have the following data mock - the promise mock stays the same:

closeResponse = {
  status: Status.CREATED
} as Partial<Instance> as Instance;

...............................................

beforeEach(async(() => {
  closeResolve(closeResponse);
}));

By doing so I don't need to subscribe to status$ to get the value of the status model. I simply point to another property status which also has the value i'm interested.

Like @Antoniossss suggested: "The whole idea is to write testable code that can be tested by simple tests".