LBRYCommunity/lbry-sdk
1
0
Fork 1
Code Issues Pull requests Projects Releases 282 Packages Wiki Activity

Updated Testing (markdown)

Lex Berezhny 2018-08-21 23:04:16 -04:00
parent dfd322b32e
commit 05cbb290f3
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Testing.md

@ -19,7 +19,7 @@ Several testing types are covered below with various do's and dont's to help you
## Integration Tests ## 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. - 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. - 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. - 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.