status-im
/
status-go
mirror of https://github.com/status-im/status-go.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Created Testing (markdown)

Evgeny Danilenko 2017-10-05 11:56:44 +03:00
parent 28be07c281
commit 73aaa00642
1 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
Testing.md Normal file

@ -0,0 +1,22 @@
# Terms and main definitions
## E2E
**Question:** "Is endpoint works properly with external systems"?
**Description:** Such tests should be written only for user endpoints. No mocks, stabs can be used. We should keep E2E tests close to production environment. For E2E testing we can use own fully functional private network.
**Location:** separate package 'e2e'.
## Integration
**Question:** "Are this components works together"?
**Description:** Component level tests. We should use it in case if there is no possibility for unit testing. Mocks and stabs can be used, such as net/http/httptest.Server mock. It's important to keep integration tests fast, reliable and predictable.
**Location:** separate package 'integration'.
## Unit
**Question:** "Is this method works correctly"?
**Description:** Function or method level tests. Should be as small as possible and do test of method in isolation of all the system. Mocks and stabs can be used.
**Location:** same level and package name as the tested code.