aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2015-10-13 11:35:11 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2015-10-13 11:35:24 +0200
commit01f74999e3dff1b0c76c334ce3935e3680d2927d (patch)
treee399975434ae0b566fd57e34ce1c4596b19a21ca /src
parentfeea3057df472ad924a0bedff5bbf5af9f5f57bf (diff)
parent700f52e0f6bc4eb5d065dc8f1e44ffcbd5dab0e0 (diff)
downloadbitcoin-01f74999e3dff1b0c76c334ce3935e3680d2927d.tar.xz
Merge pull request #6798
700f52e Clarification of unit test build instructions. (Eric Lombrozo)
Diffstat (limited to 'src')
-rw-r--r--src/test/README.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/test/README.md b/src/test/README.md
index e36112bd4f..b2d6be14f1 100644
--- a/src/test/README.md
+++ b/src/test/README.md
@@ -16,6 +16,8 @@ their tests in a test suite called "<source_filename>_tests". For an
examples of this pattern, examine uint160_tests.cpp and
uint256_tests.cpp.
+Add the source files to /src/Makefile.test.include to add them to the build.
+
For further reading, I found the following website to be helpful in
explaining how the boost unit test framework works:
[http://www.alittlemadness.com/2009/03/31/c-unit-testing-with-boosttest/](http://www.alittlemadness.com/2009/03/31/c-unit-testing-with-boosttest/).