Why do some eShopOnContainers Service API Unit Tests not reference API classes only WebMVC? [closed]

Question

Closed. This question is off-topic. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Software Engineering Stack Exchange.

Closed 1 year ago.

Improve this question

I have been trying to learn more about MicroServices architecture and I am using Microsoft's eShopOnContainers as a reference because I am familiar with .NET. I am getting into the part about testing, but I noticed that all the tests in the service API folders are referencing the WebMVC project and not the Service.API whatsoever. I have been trying to understand this and haven't been able to figure it out. The Documentation for the tests say you should be able to pull out each of those API folders into their own git repos, but wouldn't they just all have dependency on the WebMVC project? Any help understanding this is greatly appreciated.

Answer 1

You're right, it's actually a bug.

It was probably just a left over while developing the unit tests, because the methods being tested there are also covered in OrderWebApiTest.

However, they do test API Classes, but should not test the WebMVC OrderController.