dotnet-architecture / News

News on .NET Architecture Guidance, eShopOnContainers and all the reference apps in dotnet-architecture

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Improved approaches for Unit Tests and Functional Tests (including Containers/Services)

CESARDELATORRE opened this issue · comments

We have made a major update in the tests. The most significant change is that the tests related to just each a microservice are now segregated and are part of the code-boundary of each microservice, instead of having a global physical place for all tests that we used to have.
Then, the only global tests that we maintain are the end-to-end integration/functional tests for the whole app/scenarios.

You can:

  • Run Unit Tests for single/specific microservices
  • Run Functional/Integration Tests for single/specific microservices (Including infrastructure, DBs, etc.)
  • Functional/Integration Tests for single/specific microservices (Need to spin-up all the containers, first)

The multiple testing approaches are explained here:
https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/test/readme.md

The Unit Tests and Functional Tests can be improved, for sure. There might be scenarios/cases that are not covered, so we'd be thankful for PRs improving the number&quality of the tests! 👍

So awesome! thank you thank you thank you !