#nitrokey #test

nitrokey-test

Supporting test infrastructure for the nitrokey crate and others using it

9 unstable releases (4 breaking)

0.5.0 Mar 21, 2021
0.4.0 Jul 18, 2020
0.3.2 Oct 31, 2019
0.3.1 Aug 14, 2019
0.1.1 Jan 7, 2019

#119 in Testing

Download history 7/week @ 2021-06-30 15/week @ 2021-07-07 21/week @ 2021-07-14 12/week @ 2021-07-21 96/week @ 2021-07-28 25/week @ 2021-08-04 27/week @ 2021-08-11 9/week @ 2021-08-18 14/week @ 2021-08-25 40/week @ 2021-09-01 16/week @ 2021-09-08 41/week @ 2021-09-15 7/week @ 2021-09-22 14/week @ 2021-09-29 4/week @ 2021-10-06 15/week @ 2021-10-13

517 downloads per month
Used in 2 crates

GPL-3.0-or-later

31KB
520 lines

pipeline crates.io Docs rustc license

nitrokey-test

nitrokey-test is a crate providing more convenient testing capabilities for the nitrokey crate and projects building on top of it.


lib.rs:

A crate providing supporting testing infrastructure for the nitrokey crate and its users.

The crate simplifies test creation by providing an attribute macro that generates code for running a test on up to three devices ( Nitrokey Pro, Nitrokey Storage, and Librem Key), takes care of serializing all tests tagged with this attribute, and causes them to be skipped if the respective device is not present.

It also provides support for running tests belonging to a certain group. There are four groups: "nodev" (representing tests that run when no device is present), "librem" (comprised of all tests that can run on the Librem Key), "pro" (encompassing tests eligible to run on the Nitrokey Pro), and "storage" (for tests running against a Nitrokey Storage device). Running tests of a specific group (and only those) can be accomplished by setting the NITROKEY_TEST_GROUP environment variable to the group of interest. Note that in this mode tests will fail if the respective device is not present.

Right now we make a few simplifying assumptions that, although not changing what can be expressed and tested, can lead to unexpected error messages when not known:

  • the parameter has to be an owned object, not a reference
  • parameter types are pattern matched against "Storage", "Pro", and "DeviceWrapper"; that means use ... as declarations will not work properly

Dependencies

~305–730KB
~18K SLoC