summaryrefslogtreecommitdiff
path: root/tests
diff options
context:
space:
mode:
authorRobin Krahl <robin.krahl@ireas.org>2019-01-16 19:43:04 +0000
committerRobin Krahl <robin.krahl@ireas.org>2019-01-16 21:22:41 +0100
commit3a8669cea4aa4b32fee3336cb9be4ec66d3dc2c2 (patch)
treee375f03ed9feac83b15fdc545d5c7fedaed8af69 /tests
parentd3a103bc25e5f37a42a19515ad25e5a8e5995b36 (diff)
downloadnitrokey-rs-3a8669cea4aa4b32fee3336cb9be4ec66d3dc2c2.tar.gz
nitrokey-rs-3a8669cea4aa4b32fee3336cb9be4ec66d3dc2c2.tar.bz2
Build AES key after factory reset in tests
The device::clear_new_sd_card_warning used to perform a factory reset without building an AES key. This led to errors in tests that assume that an AES key is present.
Diffstat (limited to 'tests')
-rw-r--r--tests/device.rs1
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/device.rs b/tests/device.rs
index 7dea000..8efaace 100644
--- a/tests/device.rs
+++ b/tests/device.rs
@@ -462,6 +462,7 @@ fn get_production_info(device: Storage) {
#[test_device]
fn clear_new_sd_card_warning(device: Storage) {
assert_eq!(Ok(()), device.factory_reset(ADMIN_PASSWORD));
+ assert_eq!(Ok(()), device.build_aes_key(ADMIN_PASSWORD));
// We have to perform an SD card operation to reset the new_sd_card_found field
assert_eq!(Ok(()), device.lock());