Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
CESARDELATORRE opened this issue Jul 6, 2018 · 2 comments

Comments

@CESARDELATORRE
Copy link
Contributor

CESARDELATORRE commented Jul 6, 2018

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! 👍

@atifmir
Copy link

atifmir commented Jul 6, 2018 via email

@PureKrome
Copy link

So awesome! thank you thank you thank you !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants