Project Number Date
test_Tails_ISO_stable 5674 25 May 2025, 09:00

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 19:42.101 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:13.572
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.691
When I start Tails from USB drive "old" with network unplugged 1:36.123
Then the boot device has safe access rights 3.374
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 10.095
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.444
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:28.026
Then Tails is running from USB drive "old" 0.363
And I create a persistent partition 32.366
And I take note of which tps features are available 1.901
Then a Tails persistence partition exists on USB drive "old" 0.832
And I shutdown Tails and wait for the computer to power off 8.753
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.045
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.296
Then Tails is running from USB drive "old" 0.338
And all tps features are active 2.247
When I write some files expected to persist 1.843
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.459
And I take note of which tps features are available 0.486
And I shutdown Tails and wait for the computer to power off 4.359
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.206
After features/support/hooks.rb:330 0.165
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.016
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.542
And I log in to a new session 20.413
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.778
And I plug USB drive "to_upgrade" 2.579
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.790
Then the running Tails is installed on USB drive "to_upgrade" 25.431
And I unplug USB drive "to_upgrade" 0.263
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:330 2.201
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.253
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.235
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.069
Then all tps features from the old Tails version are active 1.868
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.570
And the expected persistent files created with the old Tails version are present in the filesystem 1.532
And all persistent directories from the old Tails version have safe access rights 2.651
After features/support/hooks.rb:330 1.488
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:37.539
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.609
And no SquashFS delta is installed 0.459
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.256
And Tor is ready 21.194
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.886
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.691
Given I shutdown Tails and wait for the computer to power off 8.731
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.703
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.300
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.402
# 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.311
When the network is plugged 0.075
And Tor is ready 21.267
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.324
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.311
Given I shutdown Tails and wait for the computer to power off 4.490
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.636
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.190
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.070
And Tor is ready 19.697
Then the Upgrader considers the system as up-to-date 0.324
# 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.198
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.528
After features/support/hooks.rb:330 0.737
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.229
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.367
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.168
And the signing key used by the Upgrader is outdated 0.135
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 19.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.187
After features/support/hooks.rb:330 0.981
After features/support/hooks.rb:100 0.000