Remove test-no-device feature

Currently, the test-no-device feature is used for tests that expect no
Nitrokey to be connected.  Yet test-no-device is equivalent to not
test-pro and not test-storage.  Therefore, this patch removes the
test-no-device feature.

1 files changed, 5 insertions, 5 deletions

diff --git a/README.md b/README.md
index 6039943..61da317 100644
--- a/README.md
+++ b/README.md
@@ -35,12 +35,12 @@ supported by `nitrokey-rs`:
 ## Tests
 
 This crate has three test suites that can be selected using features.  One test
-suite (feature `test-no-device`) assumes that no Nitrokey device is connected.
-The two other test suites require a Nitrokey Pro (feature `test-pro`) or a
-Nitrokey Storage (feature `test-storage`) to be connected.
+suite assumes that no Nitrokey device is connected. It is run if no other test
+suite is selected.  The two other test suites require a Nitrokey Pro (feature
+`test-pro`) or a Nitrokey Storage (feature `test-storage`) to be connected.
 
 Use the `--features` option for Cargo to select one of the test suites.  You
-cannot select more than one of the test suites at the same time.  Note that the
+should select more than one of the test suites at the same time.  Note that the
 test suites that require a Nitrokey device assume that the device’s passwords
 are the factory defaults (admin password `12345678` and user password
 `123456`).  Running the test suite with a device with different passwords might
@@ -54,7 +54,7 @@ the test executable.
 In conclusion, you can use these commands to run the test suites:
 
 ```
-$ cargo test --features test-no-device -- --test-threads 1
+$ cargo test
 $ cargo test --features test-pro -- --test-threads 1
 $ cargo test --features test-storage -- --test-threads 1
 ```