Project Number Date
test_Tails_ISO_stable 5995 09 Dec 2025, 23:45

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 15:54.537 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:2.294
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 33.858
When I start Tails from USB drive "old" with network unplugged 1:22.369
Then the boot device has safe access rights 3.731
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:331 3.928
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.936
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:32.578
Then Tails is running from USB drive "old" 0.828
And I create a persistent partition 31.219
And I take note of which tps features are available 1.393
Then a Tails persistence partition exists on USB drive "old" 0.770
And I shutdown Tails and wait for the computer to power off 8.946
After features/support/hooks.rb:331 0.711
After features/support/hooks.rb:100 0.010
Tags: @product
2:25.397
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:46.161
Then Tails is running from USB drive "old" 0.349
And all tps features are active 2.041
When I write some files expected to persist 1.564
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 3.103
And I take note of which tps features are available 0.631
And I shutdown Tails and wait for the computer to power off 9.575
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 21.191
After features/support/hooks.rb:331 0.633
After features/support/hooks.rb:100 0.008
Tags: @product
2:42.455
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.593
And I log in to a new session 17.699
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.817
And I plug USB drive "to_upgrade" 2.996
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.039
Then the running Tails is installed on USB drive "to_upgrade" 21.855
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.252
After features/support/hooks.rb:331 4.185
After features/support/hooks.rb:100 0.000
Tags: @product
1:29.005
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:19.261
Then all tps features from the old Tails version are active 1.988
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.462
And the expected persistent files created with the old Tails version are present in the filesystem 1.308
And all persistent directories from the old Tails version have safe access rights 2.490
After features/support/hooks.rb:331 2.725
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
4:33.228
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 20.292
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.050
And Tor is ready 15.797
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.600
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.249
Given I shutdown Tails and wait for the computer to power off 10.819
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.331
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.056
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.248
When the network is plugged 0.065
And Tor is ready 13.992
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.611
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.288
Given I shutdown Tails and wait for the computer to power off 8.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.627
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.186
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.171
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.058
And Tor is ready 10.587
Then the Upgrader considers the system as up-to-date 0.129
# 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 6.562
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.632
After features/support/hooks.rb:331 1.152
After features/support/hooks.rb:100 0.047
Tags: @product @automatic_upgrade
26.219
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 12.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the signing key used by the Upgrader is outdated 0.137
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 11.808
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.652
After features/support/hooks.rb:331 1.189
After features/support/hooks.rb:100 0.000