Cucumber Reports (no 4684) - Feature: Time syncing

Project	Number	Date
test_Tails_ISO_stable	4684	27 Feb 2024, 21:47

	Steps	Scenarios	Features
Time syncing	80	0	0	0	0	80	10	0	10	7:23.924	Passed

22.588

Scenario Clock with host's time

Hooks

Before features/support/hooks.rb:245 0.002

Before features/support/hooks.rb:442 0.010

Steps

Given I have started Tails from DVD without network and logged in 8.314

When the network is plugged 0.153

And I successfully configure Tor 14.061

Then the system clock is less than 5 minutes incorrect 0.059

Hooks

After features/support/hooks.rb:450 0.501

After features/support/hooks.rb:291 0.788

After features/support/hooks.rb:75 0.000

Tags: @product @check_tor_leaks

24.927

Scenario Clock with host's time while using bridges

Hooks

Before features/support/hooks.rb:245 0.002

Before features/support/hooks.rb:442 0.002

Steps

Given I have started Tails from DVD without network and logged in 7.996

When the network is plugged 0.037

And the Tor Connection Assistant autostarts 2.945

And I configure some normal bridges in the Tor Connection Assistant 12.407

And I wait until Tor is ready 1.484

Then the system clock is less than 5 minutes incorrect 0.056

Hooks

After features/support/hooks.rb:450 0.439

After features/support/hooks.rb:291 0.622

After features/support/hooks.rb:75 0.000

Tags: @product @check_tor_leaks

28.430

Scenario Clock is one day in the future while using obfs4 bridges

Hooks

Before features/support/hooks.rb:245 0.003

Before features/support/hooks.rb:442 0.002

Steps

Given I have started Tails from DVD without network and logged in 7.958

When I bump the system time with "+1 day" 0.224

And I capture all network traffic 0.005

And the network is plugged 0.104

And the Tor Connection Assistant autostarts 3.188

And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 12.861

And I wait until Tor is ready 3.045

Then the system clock is less than 5 minutes incorrect 0.053

And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.988

Hooks

After features/support/hooks.rb:450 0.559

After features/support/hooks.rb:291 0.954

After features/support/hooks.rb:75 0.043

Tags: @product @check_tor_leaks @not_release_blocker

1:14.774

Scenario The system time is not synced to the hardware clock

Hooks

Before features/support/hooks.rb:245 0.002

Before features/support/hooks.rb:442 0.002

Steps

Given I have started Tails from DVD without network and logged in 8.015

When I bump the system time with "-15 days" 0.228

And I warm reboot the computer 0.013

And the computer reboots Tails 1:5.443

Then Tails' hardware clock is close to the host system's time 1.073

Hooks

After features/support/hooks.rb:450 0.128

After features/support/hooks.rb:291 0.578

After features/support/hooks.rb:75 0.012

Tags: @product @check_tor_leaks @not_release_blocker

1:13.244

Scenario Anti-test: Changes to the hardware clock are kept when rebooting

Hooks

Before features/support/hooks.rb:245 0.006

Before features/support/hooks.rb:442 0.006

Steps

Given I have started Tails from DVD without network and logged in 8.195

When I bump the hardware clock's time with "-15 days" 2.050

And I warm reboot the computer 0.015

And the computer reboots Tails 1:2.824

Then the hardware clock is still off by "-15 days" 0.158

Hooks

After features/support/hooks.rb:450 0.109

After features/support/hooks.rb:291 0.627

After features/support/hooks.rb:75 0.033

Tags: @product @check_tor_leaks

49.937

Scenario The clock is set to the source date when the hardware clock is way in the past

Hooks

Before features/support/hooks.rb:245 0.002

Before features/support/hooks.rb:442 0.001

Steps

Given a computer 0.148

And the hardware clock is set to "01 Jan 2000 12:34:56" 0.022

And I start the computer 0.956

And the computer boots Tails 48.614

Then the system clock is just past Tails' source date 0.195

Hooks

After features/support/hooks.rb:450 0.103

After features/support/hooks.rb:291 0.563

After features/support/hooks.rb:75 0.005

Tags: @product @check_tor_leaks

31.195

Scenario On a clock with host's time, Tor Connection works even if time sync fails

Hooks

Before features/support/hooks.rb:245 0.001

Before features/support/hooks.rb:442 0.002

Steps

Given I have started Tails from DVD without network and logged in 7.980

And I make sure time sync before Tor connects times out 1.129

When the network is plugged 0.042

And I successfully configure Tor 21.961

Then the system clock is less than 5 minutes incorrect 0.080

Hooks

After features/support/hooks.rb:450 0.552

After features/support/hooks.rb:291 0.976

After features/support/hooks.rb:75 0.001

Tags: @product @check_tor_leaks

59.587

Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC

Hooks

Before features/support/hooks.rb:245 0.002

Before features/support/hooks.rb:442 0.002

Steps

Given I have started Tails from DVD without network and logged in 8.159

When I bump the system time with "+8 hours +15 minutes" 0.193

And all notifications have disappeared 2.898

And I capture all network traffic 0.003

And I make sure time sync before Tor connects fails 0.127

And the network is plugged 0.046

And the Tor Connection Assistant autostarts 3.290

When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 4.990

And I click "Connect to Tor" 1.183

And the Tor Connection Assistant fails to connect to Tor 15.514

# The "Fix Clock" button allows users to recover from this bug

Then I set the time zone in Tor Connection to "Asia/Shanghai" 14.779

Then the system clock is less than 20 minutes incorrect 0.199

When I click "Connect to Tor" 1.138

Then I wait until Tor is ready 6.127

And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.855

# check that htpdate has done its job

And the system clock is less than 5 minutes incorrect 0.079

Hooks

After features/support/hooks.rb:450 0.635

After features/support/hooks.rb:291 0.758

After features/support/hooks.rb:75 0.039

Tags: @product @check_tor_leaks

57.555

Scenario I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor

Hooks

Before features/support/hooks.rb:245 0.003

Before features/support/hooks.rb:442 0.003

Steps

Given I have started Tails from DVD without network and logged in 8.713

When I bump the system time with "+8 hours +15 minutes" 0.215

And all notifications have disappeared 4.108

And I capture all network traffic 0.003

And the network is plugged 0.242

And the Tor Connection Assistant autostarts 2.961

# Anti-test: Users east of UTC can't connect to obfs4 bridges

And I configure some obfs4 bridges in the Tor Connection Assistant in hide mode without connecting 4.259

And I click "Connect to Tor" 1.186

Then the Tor Connection Assistant reports that it failed to connect 11.663

# The "Fix Clock" button allows users to recover from this bug

When I set the time zone in Tor Connection to "Asia/Shanghai" 14.788

Then the system clock is less than 20 minutes incorrect 0.191

# "Asia/Shanghai" is UTC+08:00 all year long (no DST)

And the displayed clock is less than 20 minutes incorrect in "+08:00" 0.353

When I click "Connect to Tor" 1.142

Then I wait until Tor is ready 6.269

And all Internet traffic has only flowed through the configured bridges 0.969

# check that htpdate has done its job

And the system clock is less than 5 minutes incorrect 0.059

And the displayed clock is less than 5 minutes incorrect in "+08:00" 0.426

Hooks

After features/support/hooks.rb:450 0.538

After features/support/hooks.rb:291 0.976

After features/support/hooks.rb:75 0.040

Tags: @product @check_tor_leaks

21.680

Scenario Time sync before Tor connects sets the same headers as the NetworkManager connectivity check

Hooks

Before features/support/hooks.rb:245 0.003

Before features/support/hooks.rb:442 0.003

Steps

Given I have started Tails from DVD without network and logged in 8.667

And I make sure time sync before Tor connects uses a fake connectivity check service 1.132

And the network is plugged 0.043

And Tor is ready 11.201

Then the fake connectivity check service has received a new HTTP request 0.000

When I make NetworkManager perform a connectivity check 0.630

Then the fake connectivity check service has received a new HTTP request 0.000

And the HTTP requests received by the fake connectivity check service are identical 0.004

Hooks

After features/support/hooks.rb:450 0.690

After features/support/hooks.rb:291 0.633

After features/support/hooks.rb:75 0.000

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Time syncing	80	0	0	0	0	80	10	0	10	7:23.924	Passed

Feature Report