aboutsummaryrefslogtreecommitdiff
path: root/tests/pws.rs
diff options
context:
space:
mode:
authorRobin Krahl <robin.krahl@ireas.org>2019-01-28 19:45:40 +0000
committerRobin Krahl <robin.krahl@ireas.org>2019-01-28 19:48:33 +0000
commitd1262390573b758ac4aa610eff96a1b5dcb9f3d6 (patch)
tree445a3251f134c1794aabf587a7ef1ced01b960ea /tests/pws.rs
parent52df93249f27ae803bada0451d7380bc3d596007 (diff)
downloadnitrokey-rs-d1262390573b758ac4aa610eff96a1b5dcb9f3d6.tar.gz
nitrokey-rs-d1262390573b758ac4aa610eff96a1b5dcb9f3d6.tar.bz2
Add assert_any_ok macro to unit tests
Sometimes we cannot use assert_ok! as we can’t compare the Ok value (or do not want to). For these cases, this patch adds the new assert_any_ok macro to use instead of assert!(x.is_ok()). The advantage is that the error information is not discarded but printed in a helpful error message.
Diffstat (limited to 'tests/pws.rs')
-rw-r--r--tests/pws.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/pws.rs b/tests/pws.rs
index 3ec7e38..32dc8f7 100644
--- a/tests/pws.rs
+++ b/tests/pws.rs
@@ -46,12 +46,12 @@ fn enable(device: DeviceWrapper) {
CommandError::WrongPassword,
device.get_password_safe(&(USER_PASSWORD.to_owned() + "123"))
);
- assert!(device.get_password_safe(USER_PASSWORD).is_ok());
+ assert_any_ok!(device.get_password_safe(USER_PASSWORD));
assert_cmd_err!(
CommandError::WrongPassword,
device.get_password_safe(ADMIN_PASSWORD)
);
- assert!(device.get_password_safe(USER_PASSWORD).is_ok());
+ assert_any_ok!(device.get_password_safe(USER_PASSWORD));
}
#[test_device]