diff options
author | John Newbery <john@johnnewbery.com> | 2017-03-08 17:46:18 -0500 |
---|---|---|
committer | John Newbery <john@johnnewbery.com> | 2017-03-20 10:40:31 -0400 |
commit | 63d66ba20a634b54f6d5e8b051fb4a106f2cef6c (patch) | |
tree | e6c1211ac2cedbfbe61061fc405914262da4437e /src/test/README.md | |
parent | 5b0bff4581cf5cbecce35df46075ba256b4974f5 (diff) |
Move src/test/bitcoin-util-test.py to test/util/bitcoin-util-test.py
Diffstat (limited to 'src/test/README.md')
-rw-r--r-- | src/test/README.md | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/src/test/README.md b/src/test/README.md index 8f99804e10..eeb04c6ffa 100644 --- a/src/test/README.md +++ b/src/test/README.md @@ -50,12 +50,3 @@ examine `uint256_tests.cpp`. 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/). - -### bitcoin-util-test.py - -The test directory also contains the bitcoin-util-test.py tool, which tests bitcoin utils (currently just bitcoin-tx). This test gets run automatically during the `make check` build process. It is also possible to run the test manually from the src directory: - -``` -test/bitcoin-util-test.py --srcdir=[current directory] - -``` |