diff options
Diffstat (limited to 'features/time_syncing.feature')
| -rw-r--r-- | features/time_syncing.feature | 106 |
1 files changed, 97 insertions, 9 deletions
diff --git a/features/time_syncing.feature b/features/time_syncing.feature index a32d5a70..69a0c9e2 100644 --- a/features/time_syncing.feature +++ b/features/time_syncing.feature @@ -1,41 +1,129 @@ -@product +@product @check_tor_leaks Feature: Time syncing As a Tails user I want Tor to work properly And for that I need a reasonably accurate system clock - Background: - Given a computer - And I start Tails from DVD with network unplugged and I login - And I save the state so the background can be restored next scenario - + #10497: wait_until_tor_is_working + @fragile Scenario: Clock with host's time + Given I have started Tails from DVD without network and logged in When the network is plugged And Tor is ready Then Tails clock is less than 5 minutes incorrect + #10497: wait_until_tor_is_working + @fragile + Scenario: Clock with host's time in bridge mode + Given I have started Tails from DVD without network and logged in with bridge mode enabled + When the network is plugged + And the Tor Launcher autostarts + And I configure some Bridge pluggable transports in Tor Launcher + And Tor is ready + Then Tails clock is less than 5 minutes incorrect + + #10497: wait_until_tor_is_working + @fragile Scenario: Clock is one day in the past + Given I have started Tails from DVD without network and logged in + When I bump the system time with "-1 day" + And the network is plugged + And Tor is ready + Then Tails clock is less than 5 minutes incorrect + + #10497: wait_until_tor_is_working + @fragile + Scenario: Clock is one day in the past in bridge mode + Given I have started Tails from DVD without network and logged in with bridge mode enabled When I bump the system time with "-1 day" And the network is plugged + And the Tor Launcher autostarts + And I configure some Bridge pluggable transports in Tor Launcher + And Tor is ready + Then Tails clock is less than 5 minutes incorrect + + #10497: wait_until_tor_is_working + @fragile + Scenario: Clock is way in the past + Given I have started Tails from DVD without network and logged in + # 13 weeks will span over two Tails release cycles. + When I bump the system time with "-13 weeks" + And the network is plugged And Tor is ready Then Tails clock is less than 5 minutes incorrect - Scenario: Clock way in the past - When I set the system time to "01 Jan 2000 12:34:56" + #10497: wait_until_tor_is_working + @fragile + Scenario: Clock way in the past in bridge mode + Given I have started Tails from DVD without network and logged in with bridge mode enabled + When I bump the system time with "-6 weeks" And the network is plugged + And the Tor Launcher autostarts + And I configure some Bridge pluggable transports in Tor Launcher And Tor is ready Then Tails clock is less than 5 minutes incorrect + #10497: wait_until_tor_is_working + #10440: Time syncing tests are fragile + @fragile Scenario: Clock is one day in the future + Given I have started Tails from DVD without network and logged in When I bump the system time with "+1 day" And the network is plugged And Tor is ready Then Tails clock is less than 5 minutes incorrect + #10497: wait_until_tor_is_working + @fragile + Scenario: Clock is one day in the future in bridge mode + Given I have started Tails from DVD without network and logged in with bridge mode enabled + When I bump the system time with "+1 day" + And the network is plugged + And the Tor Launcher autostarts + And I configure some Bridge pluggable transports in Tor Launcher + And Tor is ready + Then Tails clock is less than 5 minutes incorrect + + #10497: wait_until_tor_is_working + #10440: Time syncing tests are fragile + @fragile Scenario: Clock way in the future + Given I have started Tails from DVD without network and logged in + When I set the system time to "01 Jan 2020 12:34:56" + And the network is plugged + And Tor is ready + Then Tails clock is less than 5 minutes incorrect + + #10497: wait_until_tor_is_working + #10440: Time syncing tests are fragile + @fragile + Scenario: Clock way in the future in bridge mode + Given I have started Tails from DVD without network and logged in with bridge mode enabled When I set the system time to "01 Jan 2020 12:34:56" And the network is plugged + And the Tor Launcher autostarts + And I configure some Bridge pluggable transports in Tor Launcher And Tor is ready Then Tails clock is less than 5 minutes incorrect -# Scenario: Clock vs Tor consensus' valid-{after,until} etc. +Scenario: The system time is not synced to the hardware clock + Given I have started Tails from DVD without network and logged in + When I bump the system time with "-15 days" + And I warm reboot the computer + And the computer reboots Tails + Then Tails' hardware clock is close to the host system's time + + Scenario: Anti-test: Changes to the hardware clock are kept when rebooting + Given I have started Tails from DVD without network and logged in + When I bump the hardware clock's time with "-15 days" + And I warm reboot the computer + And the computer reboots Tails + Then the hardware clock is still off by "-15 days" + + Scenario: Boot with a hardware clock set way in the past and make sure that Tails sets the clock to the build date + Given a computer + And the network is unplugged + And the hardware clock is set to "01 Jan 2000 12:34:56" + And I start the computer + And the computer boots Tails + Then the system clock is just past Tails' build date |