aboutsummaryrefslogtreecommitdiff
path: root/tests
diff options
context:
space:
mode:
authorDaniel Mueller <deso@posteo.net>2019-01-08 20:02:09 -0800
committerRobin Krahl <robin.krahl@ireas.org>2019-01-09 15:42:40 +0100
commita849924327cc6c07620fa993e4092768829542e0 (patch)
tree9dac13883ca9a7b5db987b3e5c6b999397429f2a /tests
parent0f157082bb75d08ad4fd9bfd1cdf6646fb374c3f (diff)
downloadnitrokey-rs-a849924327cc6c07620fa993e4092768829542e0.tar.gz
nitrokey-rs-a849924327cc6c07620fa993e4092768829542e0.tar.bz2
Do not check for errors in connect tests
The connect_* device tests fail when run in a setup with a Pro and Storage stick present. The problem is that these tests assume only one stick to be present, and that the corresponding connect function for the other stick reports an error. However, in a two stick setup there is no such guarantee. This patch removes tests for those assumptions.
Diffstat (limited to 'tests')
-rw-r--r--tests/device.rs6
1 files changed, 0 insertions, 6 deletions
diff --git a/tests/device.rs b/tests/device.rs
index db8194c..4d78f12 100644
--- a/tests/device.rs
+++ b/tests/device.rs
@@ -45,9 +45,6 @@ fn connect_pro(device: Pro) {
assert!(nitrokey::connect().is_ok());
assert!(nitrokey::connect_model(nitrokey::Model::Pro).is_ok());
assert!(nitrokey::Pro::connect().is_ok());
-
- assert!(nitrokey::connect_model(nitrokey::Model::Storage).is_err());
- assert!(nitrokey::Storage::connect().is_err());
}
#[test_device]
@@ -58,9 +55,6 @@ fn connect_storage(device: Storage) {
assert!(nitrokey::connect().is_ok());
assert!(nitrokey::connect_model(nitrokey::Model::Storage).is_ok());
assert!(nitrokey::Storage::connect().is_ok());
-
- assert!(nitrokey::connect_model(nitrokey::Model::Pro).is_err());
- assert!(nitrokey::Pro::connect().is_err());
}
fn assert_empty_serial_number() {