mockhttp | Testing layer for Microsoft 's HttpClient library | Mock library

Your code coverage is showing you what you really have in your tests, and let me be honest, you are not testing your core function, it is not even being invoked, the function can be full of errors and your tests won't even note it. What you are invoking and testing is a stubbed function that is created in the line spyOn(Service, 'core').and.callFake, that line is completely overriding the original core function. For example, what you need to mock is getDrugsByName function, but, if it has a lot of business logic, you need to consider writing tests for that function too.

So, change your test like this

The versioning was a red herring and it turned out to be much simpler problem. My tests were testing Async controller methods, and my non-async tests were doing:

var result = controller.PostAsync(request).Result;

as soon as I changed the tests themselves to use the async/await pattern they worked fine:

var result = await controller.PostAsync(request);

Something that helped me diagnose the issue was using the dotnet test --verbosity d argument. When using this it was outputting some tests that were passing rather than just "Starting test execution, please wait". Interestingly every time I run the command it would execute a different number of tests before appearing to get stuck. This suggested there was perhaps some sort of thread deadlock issue which led me to the solution. I'm still unsure why the command ran fine on my local machine but not our Jenkins slave.

Change approach. Do not mock the subject under test, which in this case is the controller.

The controller's Request is accessed via the HttpContext which can be set when arranging the test.

For example

To my understanding, mocks are for objects, and expectations are for functions - one per each.

In your context, it seems you could do:

MSTest performs a type conversion check using the as operator and then calls the Dispose method in this case:

You don't have to write your own mock as it is not that trivial task. Angluar already provides utilities to mock http client for unit testing. It is described in sufficient details in official documentation

https://angular.io/guide/testing#testing-http-services

In short, use HttpClientTestingModule

Tight coupling to HttpClient in the base controller makes it difficult to test derived classes in isolation. Review and refactor that code to follow DI.

No need to have a base controller and it is usually not advised.

Extract PostRequestAsync out into its own service abstraction and implementation.

I haven't added the third party dependencies, which I have in the app.js file. Most important thing is we need to add all required third party javascript file in 'karma.conf.js'. Then to add those dependencies in your unit test cases, we need to create mock javascript file and named as "ui.router.js".
and make sure that file should contain following code.

If you don't care about the 'url' in the test then you may use: