diff options
authorTails developers <>2015-01-19 11:21:40 +0000
committerTails developers <>2015-01-19 11:21:40 +0000
commit8ac780779c68f6e5e6c0bffbdb144ec8b4190421 (patch)
parentd2a56fc0a418995bd56b7cd63485fd6b1013b9f2 (diff)
parentbfcacf2b03f2eb7764c7494360590067036402b1 (diff)
Merge branch 'stable' into devel
2 files changed, 9 insertions, 4 deletions
diff --git a/features/checks.feature b/features/checks.feature
index 277bdb9..0d28784 100644
--- a/features/checks.feature
+++ b/features/checks.feature
@@ -14,6 +14,11 @@ Feature: Various checks
When Tails has booted a 64-bit kernel
Then the VirtualBox guest modules are available
+ Scenario: The 'Tor is ready' notification is shown when Tor has bootstrapped
+ Given the network is plugged
+ When I see the 'Tor is ready' notification
+ Then Tor is ready
Scenario: The shipped Tails signing key is up-to-date
Given the network is plugged
And Tor is ready
diff --git a/features/step_definitions/common_steps.rb b/features/step_definitions/common_steps.rb
index adc8614..0e43235 100644
--- a/features/step_definitions/common_steps.rb
+++ b/features/step_definitions/common_steps.rb
@@ -282,15 +282,15 @@ Then /^Tails seems to have booted normally$/ do
step "GNOME has started"
-Given /^Tor is ready$/ do
+When /^I see the 'Tor is ready' notification$/ do
next if @skip_steps_while_restoring_background
@screen.wait("GnomeTorIsReady.png", 300)
@screen.waitVanish("GnomeTorIsReady.png", 15)
- # Having seen the "Tor is ready" notification implies that Tor has
- # built a circuit, but let's check it directly to be on the safe side.
+Given /^Tor is ready$/ do
+ next if @skip_steps_while_restoring_background
step "Tor has built a circuit"
step "the time has synced"