You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 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! 👍
The text was updated successfully, but these errors were encountered:
________________________________
From: Cesar De la Torre <[email protected]>
Sent: 06 July 2018 17:39
To: dotnet-architecture/News
Cc: Subscribed
Subject: [dotnet-architecture/News] Improved approaches for Unit Tests and Functional Tests (including Containers/Services) (#19)
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 be covered, so we'd be thankful for PRs improving the number&quality of the tests! 👍
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#19>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AciEclhOSlXlKW394AlulAgNAGFnjB9bks5uD5KkgaJpZM4VFuwH>.
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:
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! 👍
The text was updated successfully, but these errors were encountered: