diff options
| author | Szczepan Zalega <szczepan@nitrokey.com> | 2018-04-10 08:02:44 +0200 |
|---|---|---|
| committer | Szczepan Zalega <szczepan@nitrokey.com> | 2018-04-10 08:02:44 +0200 |
| commit | d0eb7e950ef6535e82ee307937f51b2d3de7d777 (patch) | |
| tree | 5f0679417766c383d47d793e74ebc960bcfa4c1a | |
| parent | 320dee676971f7116f9e28d759e4feb0a36729a4 (diff) | |
| parent | ccea8b434141f525fbe6c7381516a4d34ade8450 (diff) | |
| download | libnitrokey-d0eb7e950ef6535e82ee307937f51b2d3de7d777.tar.gz libnitrokey-d0eb7e950ef6535e82ee307937f51b2d3de7d777.tar.bz2 | |
Merge branch 'pr_103'
Fixes #103
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -184,7 +184,7 @@ For additional documentation please check the following for [py.test installatio ## C++ tests There are also some unit tests implemented in C++, placed in unittest directory. They are not written as extensively as Python tests and are rather more a C++ low level interface check, often not using C++ API from `NitrokeyManager.cc`. Some of them are: [test_HOTP.cc](https://github.com/Nitrokey/libnitrokey/blob/master/unittest/test_HOTP.cc), [test.cc](https://github.com/Nitrokey/libnitrokey/blob/master/unittest/test.cc). -Unit tests were written and tested on Ubuntu 16.04/16.10/17.04. To run them just execute binaries built in ./libnitrokey/build dir after enabling them by passing `-DCOMPILE_TESTS` option like in `cmake .. -DCOMPILE_TESTS && make`. +Unit tests were written and tested on Ubuntu 16.04/16.10/17.04. To run them just execute binaries built in ./libnitrokey/build dir after enabling them by passing `-DCOMPILE_TESTS=ON` option like in `cmake .. -DCOMPILE_TESTS=ON && make`. The documentation of how it works could be found in nitrokey-app project's README on Github: |