testing-services | Code to accompany a talk on testing external services | SOAP library

I looked at the documentation and I am confused as to what asyncData is. But I can understand your confusion and I will like to clarify what I do when I subscribe inside of unit tests.

I always call done at the end of the subscribe in a unit test to ensure it went through my assertions. I think asyncData returns of data and it makes asynchronous observable synchronous. You can read about it here.

1.) I think for the 2nd case, this is the case, where they have made the observable synchronous with of and they know that that subscribe block will be traversed "synchronously".

2.) service.getObservableValue() never fails so they don't need to provide the second parameter. They are confident that the observable will always run in the subscribe block and not the error block.

Basically, for the 2nd situation, they mock a success response and if it goes into the error block of the subscribe, we have a problem because we mocked a success response. Later on in the documentation, they mock an error response and called fail on the success block of the subscribe because it should not be ran.

To always be semantically correct when testing with observables:

Let me explain, I also had similar questions few years back :

Why should we use Jasmine Spy Object in Angular Unit Testing?

Answer: Because when you create spy , you get the power to do below tasks in unit tests:

1. You can check whether the function has been called or not (by using `expect(component.method).toHaveBeenCalled())

2. You can even override the actual implementation (written inside service.ts) and return some dummy data to create several scenarios for unit test cases.

You check this article where I used Stubs unlike what you can see in angular guide. I used Stubs because I can reuse it other other-component.spec.ts which uses the same service, by simply injecting in providers using useClass. Take your time and see how I used .toHaveBeenCalled() [ to understand my point 1 ] , and also how I used .returnValue() to recreate the error behavior of service.

What is the need to create the ValueServiceSpy? Does the TestBed.inject not already inject all dependencies and the 'dependencies of the other dependencies'?

Answer: Yes, TestBed.inject did inject the dependencies but it injects the actual ValueService. For unit testing you want to isolate the " service which you want to test " (in this case, you want to test MasterService and not ValueService) .

So, it makes sense to mock the ValueService while testing MasterService.

Does that make sense ?

Where are you getting your tunnelIdentifier from?

You want to make sure:

1. The tunnel is running
2. You can access the tunnel from where you are testing
3. If you have a named tunnel (e.g. sc -i myTunnel) then "myTunnel" should be the tunnelIdentifier, not the tunnel id that is shown in the console outnot (i.e. not Tunnel ID: cdceac0e33db4d5fa44093e191dfdfb0)
4. If you have an unnamed tunnel then you should not need to specify a tunnelIdentifier for it to be used.
5. If you appear to be using the tunnel but cannot access your local environment, try a manual test session in Sauce Labs and select the tunnel to see if it works there.

The code has DI problems. Http factory has one dependency injected:

The solution for the Problem was to import "Response" from "@angular/http"