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
Copy file name to clipboardExpand all lines: documentation/docs/limitations/debug_artifacts.md
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,9 @@
2
2
ArchUnitNET gathers information about the architecture from analyzing
3
3
binaries, therefore running tests with the Release option (`dotnet test -c Release`) instead of the Debug
4
4
option (`dotnet test -c Debug`) can lead to not finding dependencies you normally would expect to find.
5
-
The edge cases we found so far are not initializing a local variable, casting an object and using
6
-
the typeof() statement. A minimal example for each edge case can be found [here](https://github.com/TNG/ArchUnitNET/blob/master/ExampleTest/LimitationsOnReleaseTest.cs).
5
+
The edge cases we found so far are not initializing a local variable, casting an object, using
6
+
the typeof() statement and checking that an async function is called.
7
+
A minimal example for each edge case can be found [here](https://github.com/TNG/ArchUnitNET/blob/master/ExampleTest/LimitationsOnReleaseTest.cs).
7
8
8
9
9
10
If you come across another edge case, where executing tests in Debug mode leads to different results than executing
0 commit comments