From 23e2f555797cb8eae53504a54f0b76421b922d17 Mon Sep 17 00:00:00 2001 From: Sergio Arroutbi Date: Tue, 23 Apr 2024 12:02:33 +0200 Subject: [PATCH] Fix tests/README (adapt to meson) Resolves: #381 Signed-off-by: Sergio Arroutbi --- tests/README | 12 +----------- tests/README.md | 14 ++++++++++++++ 2 files changed, 15 insertions(+), 11 deletions(-) mode change 100644 => 120000 tests/README create mode 100644 tests/README.md diff --git a/tests/README b/tests/README deleted file mode 100644 index bc065c2c..00000000 --- a/tests/README +++ /dev/null @@ -1,11 +0,0 @@ -Tests are currently available for two different software token implementations, -NSS's softokn and softhsm (with some limitations). - -The easiest way to configure things to run manual tests is to simply make check; -this will create two temporary directories with each token's configurations. - -After make check has run, set up your environment with: -$ source tests/tmp./testvars - -Then you can run code like: -$ openssl pkey -in $ECPUBURI -pubin -pubout -out ecout.pub diff --git a/tests/README b/tests/README new file mode 120000 index 00000000..42061c01 --- /dev/null +++ b/tests/README @@ -0,0 +1 @@ +README.md \ No newline at end of file diff --git a/tests/README.md b/tests/README.md new file mode 100644 index 00000000..9bed8c7e --- /dev/null +++ b/tests/README.md @@ -0,0 +1,14 @@ +Tests are currently available for two different software token implementations, +NSS's softokn and softhsm (with some limitations). + +The easiest way to configure things to run manual tests is to simply execute next command from project's root directory: +```bash +meson test -C build +``` +Be aware that previous command might change if a different build directory has been selected. Previous command will create two temporary directories with each token's configurations. + +After make check has run, set up your environment with: +$ source tests/tmp./testvars + +Then you can run code like: +$ openssl pkey -in $ECPUBURI -pubin -pubout -out ecout.pub