Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix tests/README (adapt to meson) #382

Merged
merged 1 commit into from
Apr 23, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 0 additions & 11 deletions tests/README

This file was deleted.

1 change: 1 addition & 0 deletions tests/README
18 changes: 18 additions & 0 deletions tests/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
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 this command from project's root directory:
```bash
meson test -C builddir
```
The 'builddir' argument is the name of the build directory, if you built in another directory you'll have to provide the name of the build directory here. This command will create a temporary directory for each token being tested.

If you want to manually test some commands against one of the supported software tokens, execute the test suite first and then source the necessary environment variables via:
```bash
$ source tests/tmp.<softokn|softhsm>/testvars
```

Then code can be executed like:
```bash
$ openssl pkey -in $ECPUBURI -pubin -pubout -out ecout.pub
```
Loading