forked from kgrzybek/modular-monolith-with-ddd
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
25 additions
and
1 deletion.
There are no files selected for viewing
2 changes: 1 addition & 1 deletion
2
docs/architecture-decision-log/0016-create-ioc-container-per-module.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
# 15. Create an IoC Container per module | ||
# 16. Create an IoC Container per module | ||
|
||
Date: 2019-07-15 | ||
|
||
|
24 changes: 24 additions & 0 deletions
24
docs/architecture-decision-log/0017-implement-archictecture-tests.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# 17. Implement Architecture Tests | ||
|
||
Date: 2019-11-16 | ||
|
||
## Status | ||
|
||
Accepted | ||
|
||
## Context | ||
|
||
In some cases it is not possible to enforce the application architecture, design or established conventions using compiler (compile-time). For this reason, code implementations can diverge from the original design and architecture. We want to minimize this behavior, not only by code review. | ||
|
||
## Decision | ||
|
||
We decided to implement Unit Tests for our architecture. </br> | ||
We will implement tests for each module separately and one tests library for general architecture. We will use _NetArchTest_ library which was created exactly for this purpose. | ||
|
||
## Consequences | ||
- We will have quick feedback about breaking the design rules | ||
- Unit tests for architecture are documenting our architecture to some level | ||
- We will have dependency to external library | ||
- We need to implement some _"reflection-based"_ code to check some rules, because library does not provide everything what we need | ||
- This kind of tests are a bit slower than normal unit tests (because of reflection) | ||
- More tests to maintain |