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:06:28 -04:00
parent 05cbb290f3
commit d8e50b5da9
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
Testing.md

@ -22,4 +22,5 @@ Several testing types are covered below with various do's and dont's to help you
- 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.
- 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.
- Well written integration tests can act as a form of documentation and the authoritative specification of a feature with built-in self-validation.