Project Number Date
test_Tails_ISO_20904-tor-browser-14.5-force-all-tests 10 27 Apr 2025, 14:43

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 21:18.218 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
2:28.809
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.234
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 38.528
When I start Tails from USB drive "old" with network unplugged 1:44.365
Then the boot device has safe access rights 3.450
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.232
After features/support/hooks.rb:330 3.726
After features/support/hooks.rb:100 0.013
Tags: @product
2:20.843
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.260
And I start Tails from USB drive "old" with network unplugged and I login 1:34.721
Then Tails is running from USB drive "old" 0.414
And I create a persistent partition 33.528
And I take note of which tps features are available 2.478
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.615
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.009
Tags: @product
3:6.653
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.377
Then Tails is running from USB drive "old" 0.431
And all tps features are active 2.210
When I write some files expected to persist 2.071
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.320
And all persistence configuration files have safe access rights 0.639
And all persistent directories from the old Tails version have safe access rights 2.595
And I take note of which tps features are available 0.465
And I shutdown Tails and wait for the computer to power off 4.471
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.820
After features/support/hooks.rb:330 0.230
After features/support/hooks.rb:100 0.020
Tags: @product
2:45.605
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.150
And I log in to a new session 20.890
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.040
And I plug USB drive "to_upgrade" 2.546
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.258
Then the running Tails is installed on USB drive "to_upgrade" 27.242
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.266
After features/support/hooks.rb:330 0.829
After features/support/hooks.rb:100 0.000
Tags: @product
2:34.487
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.426
Then all tps features from the old Tails version are active 2.028
And Tails is running from USB drive "to_upgrade" 0.395
And the boot device has safe access rights 3.825
And the expected persistent files created with the old Tails version are present in the filesystem 1.652
And all persistent directories from the old Tails version have safe access rights 2.965
After features/support/hooks.rb:330 1.618
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:24.275
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.561
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.487
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.571
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.711
When the network is plugged 0.091
And Tor is ready 52.390
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.706
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.034
Given I shutdown Tails and wait for the computer to power off 9.533
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.103
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.434
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.072
And Tor is ready 17.212
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.814
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.540
Given I shutdown Tails and wait for the computer to power off 6.743
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.821
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.206
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.069
And Tor is ready 19.680
Then the Upgrader considers the system as up-to-date 0.337
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 16.065
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.608
After features/support/hooks.rb:330 0.863
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
37.543
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.703
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.132
And the signing key used by the Upgrader is outdated 0.201
But a current signing key is available on our website 0.000
When the network is plugged 0.122
And Tor is ready 18.978
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.045
After features/support/hooks.rb:330 1.707
After features/support/hooks.rb:100 0.000