Skip to content

Files

This branch is 69 commits ahead of, 12136 commits behind litecoin-project/litecoin:master.

test

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Sep 20, 2017
Aug 14, 2017
Jun 5, 2014
Sep 20, 2017
Aug 14, 2017
Jun 28, 2017
Sep 20, 2017
Jun 22, 2017
Dec 13, 2015
Sep 20, 2017
Dec 13, 2015
Jun 5, 2017
Sep 20, 2017
Sep 20, 2017
Dec 17, 2016
Jun 9, 2017
Jun 26, 2017
Sep 20, 2017
Jun 8, 2017
Jun 9, 2017
Jul 16, 2017
Aug 14, 2017
Jun 7, 2017
Sep 20, 2017
Jan 22, 2017
Sep 20, 2017
Mar 7, 2017
Jun 7, 2017
Sep 20, 2017
Aug 7, 2017
Aug 14, 2017
Jul 12, 2017
Jun 8, 2017
Jul 15, 2017
Sep 20, 2017
Jun 22, 2017
Aug 7, 2017
Jun 5, 2017
Dec 31, 2016
Sep 20, 2017
Dec 13, 2015
Jun 7, 2017
Aug 7, 2017
Aug 7, 2017
Dec 13, 2015
Jan 12, 2017
Sep 20, 2017
Jan 27, 2017
Jun 8, 2017
Jul 14, 2017
Aug 7, 2017
Jun 9, 2017
Sep 20, 2017
Jul 7, 2017
Jun 1, 2017
Mar 10, 2017
Apr 3, 2017
Apr 3, 2017
Jan 2, 2017
May 16, 2017
Sep 20, 2017
Aug 7, 2017
Dec 31, 2016
Jan 5, 2017
Aug 7, 2017
Sep 20, 2017

Notes

The sources in this directory are unit test cases. Boost includes a unit testing framework, and since litecoin 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_litecoin" 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 "<source_filename>_tests.cpp" and such files should wrap 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/.