Project Number Date
test_Tails_ISO_devel 4063 10 Nov 2025, 12:15

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 16:21.632 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:1.691
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 31.921
When I start Tails from USB drive "old" with network unplugged 1:24.370
Then the boot device has safe access rights 3.143
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:331 4.093
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.963
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:24.032
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 29.988
And I take note of which tps features are available 1.235
Then a Tails persistence partition exists on USB drive "old" 0.689
And I shutdown Tails and wait for the computer to power off 7.524
After features/support/hooks.rb:331 0.520
After features/support/hooks.rb:100 0.011
Tags: @product
2:5.797
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:32.867
Then Tails is running from USB drive "old" 0.292
And all tps features are active 1.793
When I write some files expected to persist 1.516
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.178
And I take note of which tps features are available 0.460
And I shutdown Tails and wait for the computer to power off 8.026
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.858
After features/support/hooks.rb:331 0.627
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.925
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.123
And I log in to a new session 17.566
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.204
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.364
Then the running Tails is installed on USB drive "to_upgrade" 20.880
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:331 4.072
After features/support/hooks.rb:100 0.000
Tags: @product
1:42.748
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:33.798
Then all tps features from the old Tails version are active 1.389
And Tails is running from USB drive "to_upgrade" 0.292
And the boot device has safe access rights 3.416
And the expected persistent files created with the old Tails version are present in the filesystem 1.296
And all persistent directories from the old Tails version have safe access rights 2.384
After features/support/hooks.rb:331 0.690
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:58.457
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 13.120
And no SquashFS delta is installed 0.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.505
When the network is plugged 0.066
And Tor is ready 13.566
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.791
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.894
Given I shutdown Tails and wait for the computer to power off 8.099
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.526
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.098
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.179
# 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.256
When the network is plugged 0.055
And Tor is ready 14.055
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.557
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.085
Given I shutdown Tails and wait for the computer to power off 7.761
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.797
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.168
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.065
And Tor is ready 11.990
Then the Upgrader considers the system as up-to-date 0.202
# 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 5.946
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.534
After features/support/hooks.rb:331 0.797
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
54.049
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 41.716
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.784
After features/support/hooks.rb:331 0.837
After features/support/hooks.rb:100 0.000