diff options
| author | Philip Hands <phil@hands.com> | 2016-05-11 17:11:01 +0200 |
|---|---|---|
| committer | Philip Hands <phil@hands.com> | 2016-05-11 17:11:01 +0200 |
| commit | a5d56e3b5443263b53b0487c81125123411bd0cf (patch) | |
| tree | 71b1bdafc0a5978bca9073609eff33e228e29a12 /features/dhcp.feature | |
| parent | 555d9414f758cc0062eff700a0352ae177fd9be5 (diff) | |
| download | jenkins.debian.net-a5d56e3b5443263b53b0487c81125123411bd0cf.tar.xz | |
move cucumber things under cucumber/
Diffstat (limited to 'features/dhcp.feature')
| -rw-r--r-- | features/dhcp.feature | 22 |
1 files changed, 0 insertions, 22 deletions
diff --git a/features/dhcp.feature b/features/dhcp.feature deleted file mode 100644 index 18874dbf..00000000 --- a/features/dhcp.feature +++ /dev/null @@ -1,22 +0,0 @@ -@product @fragile -Feature: Getting a DHCP lease without leaking too much information - As a Tails user - when I connect to a network with a DHCP server - I should be able to connect to the Internet - and the hostname should not have been leaked on the network. - - Background: - Given I have started Tails from DVD without network and logged in - And I capture all network traffic - And the network is plugged - And Tor is ready - And all notifications have disappeared - And available upgrades have been checked - - Scenario: Getting a DHCP lease with the default NetworkManager connection - Then the hostname should not have been leaked on the network - - Scenario: Getting a DHCP lease with a manually configured NetworkManager connection - When I add a wired DHCP NetworkManager connection called "manually-added-con" - And I switch to the "manually-added-con" NetworkManager connection - Then the hostname should not have been leaked on the network |