Updated Testing (markdown)
parent
dfd322b32e
commit
05cbb290f3
1 changed files with 1 additions and 1 deletions
|
@ -19,7 +19,7 @@ Several testing types are covered below with various do's and dont's to help you
|
|||
|
||||
## Integration Tests
|
||||
|
||||
- An integration test covers two or more units of code and at the same time makes it an integration test.
|
||||
- An integration test covers two or more units of code and should avaid mocks as much as possible.
|
||||
- Integration tests are primarily for proving your code does what it was designed to do and that it plays well with the rest of the code in the application.
|
||||
- Each public facing interaction point (API, protocol, etc) should have an adequate battery of integration tests.
|
||||
- Every use case or feature of the application should have integration tests showing how to exercise the feature or perform the use case and the expected results of those operations.
|
Loading…
Reference in a new issue