Project Number Date
test_Tails_ISO_stable 6093 26 Jan 2026, 20:09

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 12:45.233 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:0.887
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.479
When I start Tails from USB drive "old" with network unplugged 1:43.016
Then the boot device has safe access rights 2.682
And Tails is running from USB drive "old" 0.208
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:331 3.731
After features/support/hooks.rb:100 0.006
Tags: @product
1:36.171
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 1:7.653
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 23.008
And I take note of which tps features are available 0.665
Then a Tails persistence partition exists on USB drive "old" 0.556
And I shutdown Tails and wait for the computer to power off 3.988
After features/support/hooks.rb:331 0.356
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.041
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.606
Then Tails is running from USB drive "old" 0.268
And all tps features are active 0.955
When I write some files expected to persist 1.156
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.116
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.672
And I take note of which tps features are available 0.186
And I shutdown Tails and wait for the computer to power off 7.814
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.925
After features/support/hooks.rb:331 0.316
After features/support/hooks.rb:100 0.007
Tags: @product
2:22.770
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 without a persistent partition and stopped at Tails Greeter's login screen 8.635
And I log in to a new session 14.167
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.712
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.446
Then the running Tails is installed on USB drive "to_upgrade" 16.272
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.169
After features/support/hooks.rb:331 13.532
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.724
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.884
Then all tps features from the old Tails version are active 0.973
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.699
And the expected persistent files created with the old Tails version are present in the filesystem 1.094
And all persistent directories from the old Tails version have safe access rights 1.799
After features/support/hooks.rb:331 0.579
After features/support/hooks.rb:100 0.006
3:49.358
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.719
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.310
When the network is plugged 0.018
And Tor is ready 14.543
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.351
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.064
Given I shutdown Tails and wait for the computer to power off 17.908
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.563
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.088
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.221
When the network is plugged 0.013
And Tor is ready 11.105
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.691
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.297
Given I shutdown Tails and wait for the computer to power off 7.922
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.246
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.125
And the file system changes introduced in version 6.3~testoverlayfs are present 0.354
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.120
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.017
And Tor is ready 9.784
Then the Upgrader considers the system as up-to-date 10.502
# 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 3.703
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.359
After features/support/hooks.rb:331 1.075
After features/support/hooks.rb:100 0.011
19.280
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 7.540
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
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.067
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.329
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.049
After features/support/hooks.rb:331 0.916
After features/support/hooks.rb:100 0.000