Home/ Questions/Q 6979011
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T17:49:53+00:00

I have a client application which calls my WCF service (Security Token Service i.e.

  • 0

I have a client application which calls my WCF service (Security Token Service i.e. STS, to be precise) which authenticates the user. We have many applications integrated together and this specific WCF service (STS) in turn calls other web service of some third party application because my STS needs some details from the third party web service to proceed.

Now I want to write unit tests for my STS as well as for my client application login functionality.

My questions are:

  1. Shall I write unit test just for STS methods with some hard coded values as input from third party web service? If no, unit tests will fail if something goes wrong with the third party web service.

  2. Instead of calling my STS from unit tests of client application, can i hard code the input (e.g. username and password) values? Is it the right approach?

  3. Is it necessary to actually call the web service from unit tests written for client application? If yes, why?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A unit test does not cross process boundaries, integration tests do that. Your purpose is to test the behaviour of your STS only. In order to do so you need to inject a mock implementation of the 3rd party service. I suggest you look a MOQ. you may also need a DI container (I use ms unity, but are many to chose from) from which your STS will resolve a reference to the 3rd party service.

    • build 3rd party service mock and register in DI container
    • instantiate STS in process, no need to fire up WCF runtime
    • test STS and verify mock expectations
    • 0