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: CONTRIBUTING.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -42,4 +42,6 @@ Testing is always important and the code coverage by unit tests should not decre
42
42
DynamoDB comes with a lot of features. Therefore new supported features should always come with an Integration Test.
43
43
44
44
That means that it should have an `...IT.java` test class that uses the local DynamoDB to demonstrate how the feature is used.
45
-
This serves as proove that it is working (test case succeeds) and also as documentation and 'how-to'.
45
+
This serves as proove that it is working (test case succeeds) and also as documentation and 'how-to'.
46
+
But an Integration Test should always be present _next to_ regular Unit Tests that follow common, good practise to test a single class without requiring existence of external dependencies.
0 commit comments