Commit a4fb817f authored by anonym's avatar anonym
Browse files

Simplify test.

Instead of waiting a long time, let's just check that networking truly
is disabled, in the same way we do for the MAC spoofing tests -- after
all the code for the "Diable networking" feature actually originates
from the MAC spoofing feature. This way we do not have to introduce a
static wait for 120 seconds, and we do not need the anti-test.
parent f70dc433
......@@ -91,18 +91,4 @@ Feature: Various checks
And I disable all networking in the Tails Greeter
And I log in to a new session
And the Tails desktop is ready
Then no network interface is enabled
When the network is plugged
And I wait 120 seconds
Then no network interfaces are enabled
And process "tor" is not running
And network traffic is not generated during the Tails session
Scenario: Anti-test: Network traffic is generated when "disable all networking" is not selected
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen
When I log in to a new session
And the Tails desktop is ready
Then 1 network interface is enabled
When the network is plugged
And Tor is ready
Then network traffic is generated during the Tails session
......@@ -245,13 +245,3 @@ When /^I disable all networking in the Tails Greeter$/ do
@screen.click('TailsGreeterDisableAllNetworking.png')
end
end
Then /^network traffic is (not )?generated during the Tails session$/ do |not_generated|
pkts = ip4tables_packet_counter_sum
if not_generated
assert_equal(0, pkts)
else
assert_not_equal(0, pkts)
end
debug_log("#{pkts} packets found")
end
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment