Project Number Date
test_Tails_ISO_devel 3895 03 Jul 2025, 15:03

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 38:13.912 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
3:56.420
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.275
And I create a 7200 MiB disk named "old" 0.089
And I plug USB drive "old" 1.278
And I write an old version of the Tails USB image to disk "old" 1:8.610
When I start Tails from USB drive "old" with network unplugged 2:33.069
Then the boot device has safe access rights 11.533
And Tails is running from USB drive "old" 0.463
And there is no persistence partition on USB drive "old" 0.129
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.508
And I unplug USB drive "old" 0.354
After features/support/hooks.rb:330 5.634
After features/support/hooks.rb:100 1.166
Tags: @product
4:28.351
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.563
Given a computer 3.719
And I start Tails from USB drive "old" with network unplugged and I login 2:51.839
Then Tails is running from USB drive "old" 9.221
And I create a persistent partition 1:4.218
And I take note of which tps features are available 2.740
Then a Tails persistence partition exists on USB drive "old" 1.223
And I shutdown Tails and wait for the computer to power off 15.389
After features/support/hooks.rb:330 0.146
After features/support/hooks.rb:100 0.015
Tags: @product
6:6.749
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:42.356
Then Tails is running from USB drive "old" 0.639
And all tps features are active 2.997
When I write some files expected to persist 12.047
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.395
And all persistence configuration files have safe access rights 0.479
And all persistent directories from the old Tails version have safe access rights 2.739
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 4.692
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 59.686
After features/support/hooks.rb:330 0.191
After features/support/hooks.rb:100 0.015
Tags: @product
4:34.400
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 without a persistent partition and stopped at Tails Greeter's login screen 25.444
And I log in to a new session 45.624
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.450
And I plug USB drive "to_upgrade" 3.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:17.837
Then the running Tails is installed on USB drive "to_upgrade" 58.017
And I unplug USB drive "to_upgrade" 0.280
And I unplug USB drive "__internal" 0.321
After features/support/hooks.rb:330 4.153
After features/support/hooks.rb:100 0.000
Tags: @product
4:41.498
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.330
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:18.336
Then all tps features from the old Tails version are active 2.274
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 14.564
And the expected persistent files created with the old Tails version are present in the filesystem 1.819
And all persistent directories from the old Tails version have safe access rights 3.829
After features/support/hooks.rb:330 5.367
After features/support/hooks.rb:100 0.128
Tags: @product @automatic_upgrade
13:26.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.036
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 42.570
And no SquashFS delta is installed 1.892
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.797
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.163
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.485
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.608
When the network is plugged 0.086
And Tor is ready 41.054
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 18.648
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 37.183
Given I shutdown Tails and wait for the computer to power off 2:25.407
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:43.218
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 7.401
And the file system changes introduced in version 6.2~testoverlayfs are present 0.698
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.354
# 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.305
When the network is plugged 0.081
And Tor is ready 21.725
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.843
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.595
Given I shutdown Tails and wait for the computer to power off 6.876
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:54.900
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.610
And the file system changes introduced in version 6.3~testoverlayfs are present 0.614
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.368
When the network is plugged 0.163
And Tor is ready 28.235
Then the Upgrader considers the system as up-to-date 0.369
# 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 21.837
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.630
After features/support/hooks.rb:330 0.703
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
1:0.265
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 26.378
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 27.673
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.635
After features/support/hooks.rb:330 2.414
After features/support/hooks.rb:100 0.000