LoweBowe/status-go
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
Page: Testing
Pages
Additional JSON RPC API Building Code Review Contact Contributing Deployment FAQ Glossary of Terms Home Modifying code in go ethereum Notes on Bindings Rebase go ethereum Status CLI command: statusd Style Guide Testing Updating CHT BloomTrie Usage Patterns Whisper Push Notifications
1 Testing
Evgeny Danilenko edited this page 2017-10-05 11:56:44 +03:00
Table of Contents

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.

Project Information

Getting started

Developers

Support

Internal