Project Number Date
test_Tails_ISO_stable 6089 24 Jan 2026, 08:18

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 13:8.169 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
1:39.259
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.511
When I start Tails from USB drive "old" with network unplugged 1:20.154
Then the boot device has safe access rights 2.798
And Tails is running from USB drive "old" 0.266
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:331 3.504
After features/support/hooks.rb:100 0.066
Tags: @product
1:32.831
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 1:1.859
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 25.220
And I take note of which tps features are available 0.782
Then a Tails persistence partition exists on USB drive "old" 0.536
And I shutdown Tails and wait for the computer to power off 4.092
After features/support/hooks.rb:331 0.174
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.490
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.768
Then Tails is running from USB drive "old" 0.201
And all tps features are active 1.003
When I write some files expected to persist 1.142
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.288
And all persistent directories from the old Tails version have safe access rights 1.972
And I take note of which tps features are available 0.160
And I shutdown Tails and wait for the computer to power off 8.195
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.498
After features/support/hooks.rb:331 0.407
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.879
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 8.778
And I log in to a new session 12.118
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.739
And I plug USB drive "to_upgrade" 2.327
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.508
Then the running Tails is installed on USB drive "to_upgrade" 17.012
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:331 2.870
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.748
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.846
Then all tps features from the old Tails version are active 0.926
And Tails is running from USB drive "to_upgrade" 0.243
And the boot device has safe access rights 2.362
And the expected persistent files created with the old Tails version are present in the filesystem 1.259
And all persistent directories from the old Tails version have safe access rights 2.058
After features/support/hooks.rb:331 1.023
After features/support/hooks.rb:100 0.034
3:59.976
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 9.151
And no SquashFS delta is installed 0.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.194
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.017
And Tor is ready 13.212
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.771
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.466
Given I shutdown Tails and wait for the computer to power off 15.450
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.460
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.208
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.219
When the network is plugged 0.019
And Tor is ready 11.271
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.351
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.282
Given I shutdown Tails and wait for the computer to power off 8.199
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.469
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.065
And the file system changes introduced in version 6.3~testoverlayfs are present 0.311
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.013
And Tor is ready 11.039
Then the Upgrader considers the system as up-to-date 10.638
# 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 4.254
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:331 1.325
After features/support/hooks.rb:100 0.012
49.983
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 41.216
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.343
After features/support/hooks.rb:331 0.720
After features/support/hooks.rb:100 0.000