Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Add test case for --version option | Robin Krahl | 2019-02-17 |
| | | | | | This change adds a test case for the -V/--version option to the suite of tests. | ||
* | Refactor integration test code internals for program invocation | Daniel Mueller | 2019-01-10 |
| | | | | | | | | | | | | | In the future we will need to perform a sequence of invocations of the program for testing purposes, with each having a slightly different execution context. Such a scheme does not map very well to the existing design where we essentially just have a function invocation to run the program. We would either have functions that produce a different execution context or pass in the data to modify. Neither of these approaches is appealing and so this change reworks the code slightly. With it, we now can create a Nitrocli object, which contains the data that diverges from the default execution context. This data will eventually be modifiable by callers. | ||
* | Add first set of integration tests | Daniel Mueller | 2019-01-05 |
This change introduces the first set of integration-style test for the application. Those tests may or may not connect to an actual Nitrokey device (depending on what they test). We use the nitrokey-test crate's test attribute macro to automatically dispatch tests to connected devices or skip them if a required device is not present. It also provides the means for automatically serializing tests. |