From d3081fa2314ac064c1054b58f4b11c332af6fe09 Mon Sep 17 00:00:00 2001 From: super3 Date: Tue, 22 Apr 2014 00:24:09 -0400 Subject: Removed LevelDB changes Syntax Highlighting --- src/test/README | 21 --------------------- src/test/README.md | 21 +++++++++++++++++++++ 2 files changed, 21 insertions(+), 21 deletions(-) delete mode 100644 src/test/README create mode 100644 src/test/README.md (limited to 'src') diff --git a/src/test/README b/src/test/README deleted file mode 100644 index 77f7faa815..0000000000 --- a/src/test/README +++ /dev/null @@ -1,21 +0,0 @@ -The sources in this directory are unit test cases. Boost includes a -unit testing framework, and since bitcoin already uses boost, it makes -sense to simply use this framework rather than require developers to -configure some other framework (we want as few impediments to creating -unit tests as possible). - -The build system is setup to compile an executable called "test_bitcoin" -that runs all of the unit tests. The main source file is called -test_bitcoin.cpp, which simply includes other files that contain the -actual unit tests (outside of a couple required preprocessor -directives). The pattern is to create one test file for each class or -source file for which you want to create unit tests. The file naming -convention is "_tests.cpp" and such files should wrap -their tests in a test suite called "_tests". For an -examples of this pattern, examine uint160_tests.cpp and -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/ diff --git a/src/test/README.md b/src/test/README.md new file mode 100644 index 0000000000..7efce6f052 --- /dev/null +++ b/src/test/README.md @@ -0,0 +1,21 @@ +# Notes +The sources in this directory are unit test cases. Boost includes a +unit testing framework, and since bitcoin already uses boost, it makes +sense to simply use this framework rather than require developers to +configure some other framework (we want as few impediments to creating +unit tests as possible). + +The build system is setup to compile an executable called "test_bitcoin" +that runs all of the unit tests. The main source file is called +test_bitcoin.cpp, which simply includes other files that contain the +actual unit tests (outside of a couple required preprocessor +directives). The pattern is to create one test file for each class or +source file for which you want to create unit tests. The file naming +convention is "_tests.cpp" and such files should wrap +their tests in a test suite called "_tests". For an +examples of this pattern, examine uint160_tests.cpp and +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 -- cgit v1.2.3