diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2016-08-03 11:00:17 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2016-08-03 11:00:30 +0200 |
| commit | fc93486d2a0066a8b52e072000f0b5b6c568dccb (patch) | |
| tree | 6f8d127fbf35f49addc1f70be1f9d2f57c90137c /src/test | |
| parent | 2eed09fe1e3d0ece00fa9ab8d4408da565c33f67 (diff) | |
| parent | b8db185952c815444b7052092472ef9af3a42e89 (diff) | |
Merge #8428: Update README.md inside of src/test/
b8db185 Update README.md (Chris Stewart)
Diffstat (limited to 'src/test')
| -rw-r--r-- | src/test/README.md | 21 |
1 files changed, 9 insertions, 12 deletions
diff --git a/src/test/README.md b/src/test/README.md index b2d6be14f1..61462642bf 100644 --- a/src/test/README.md +++ b/src/test/README.md @@ -5,18 +5,15 @@ 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" +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 "<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. +test_bitcoin.cpp. To add a new unit test file to our test suite you need +to add the file to `src/Makefile.test.include`. 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 example of this pattern, +examine `uint256_tests.cpp`. For further reading, I found the following website to be helpful in explaining how the boost unit test framework works: @@ -31,5 +28,5 @@ example, to run just the getarg_tests verbosely: test_bitcoin --run_test=getarg_tests/doubledash -Run test_bitcoin --help for the full list. +Run `test_bitcoin --help` for the full list. |