... | @@ -11,3 +11,13 @@ If you plan to commit your own remote branches to the repo (if you're working fo |
... | @@ -11,3 +11,13 @@ If you plan to commit your own remote branches to the repo (if you're working fo |
|
## Coding conventions
|
|
## Coding conventions
|
|
* 2 space indention (DO NOT USE TABS)
|
|
* 2 space indention (DO NOT USE TABS)
|
|
* Avoid the use of acronyms and abbreviations in source code (i.e. in variable names) and file names unless it is standard abbreviation/acronym of the English language.
|
|
* Avoid the use of acronyms and abbreviations in source code (i.e. in variable names) and file names unless it is standard abbreviation/acronym of the English language.
|
|
|
|
|
|
|
|
## Testing methodology
|
|
|
|
|
|
|
|
Unit tests in the C++ source code are used as first-level tests.
|
|
|
|
|
|
|
|
Python-based API tests are used to verify the functionality of API functions that are exposed to outside processes.
|
|
|
|
|
|
|
|
A reindexing test verifies that hived is able to process existing blocks in the blockchain. Currently this is a simple pass/fail test (the test fails if the node isn't able to process all the blocks in the blockchain). As this is a computationally intensive test, it's also a performance test.
|
|
|
|
|
|
|
|
Future testing will combine reindex testing with the generation of state files to verify that blocks are correctly processed. These tests will compare the state files generated by new versions of hived versus the state files of old versions of hived. |
|
|
|
\ No newline at end of file |