diff options
| author | Gavin Andresen <[email protected]> | 2015-03-03 09:59:32 -0500 |
|---|---|---|
| committer | Pieter Wuille <[email protected]> | 2015-07-27 15:50:21 +0200 |
| commit | 517e6dd25618522c716e64859554b0f29c6e65d0 (patch) | |
| tree | 0df44e4bf60db529846142b60cc2894c128d3d8b /src/test/README.md | |
| parent | Cache transaction validation successes (diff) | |
| download | discoin-517e6dd25618522c716e64859554b0f29c6e65d0.tar.xz discoin-517e6dd25618522c716e64859554b0f29c6e65d0.zip | |
Unit test doublespends in new blocks
As suggested by Greg Maxwell-- unit test to make sure a block
with a double-spend in it doesn't pass validation if half of
the double-spend is already in the memory pool (so full-blown
transaction validation is skipped) when the block is received.
Diffstat (limited to 'src/test/README.md')
| -rw-r--r-- | src/test/README.md | 14 |
1 files changed, 13 insertions, 1 deletions
diff --git a/src/test/README.md b/src/test/README.md index 7efce6f05..e36112bd4 100644 --- a/src/test/README.md +++ b/src/test/README.md @@ -18,4 +18,16 @@ 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/).
\ No newline at end of file +[http://www.alittlemadness.com/2009/03/31/c-unit-testing-with-boosttest/](http://www.alittlemadness.com/2009/03/31/c-unit-testing-with-boosttest/). + +test_bitcoin has some built-in command-line arguments; for +example, to run just the getarg_tests verbosely: + + test_bitcoin --log_level=all --run_test=getarg_tests + +... or to run just the doubledash test: + + test_bitcoin --run_test=getarg_tests/doubledash + +Run test_bitcoin --help for the full list. + |