Project Number Date
test_Tails_ISO_stable 6043 08 Jan 2026, 11:32

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 11:1.165 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:8.349
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
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.158
When I start Tails from USB drive "old" with network unplugged 50.956
Then the boot device has safe access rights 2.500
And Tails is running from USB drive "old" 0.254
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:331 4.009
After features/support/hooks.rb:100 0.005
Tags: @product
1:24.966
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 51.343
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 23.921
And I take note of which tps features are available 0.698
Then a Tails persistence partition exists on USB drive "old" 0.538
And I shutdown Tails and wait for the computer to power off 8.111
After features/support/hooks.rb:331 0.363
After features/support/hooks.rb:100 0.007
Tags: @product
1:21.473
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 57.057
Then Tails is running from USB drive "old" 0.242
And all tps features are active 0.991
When I write some files expected to persist 1.276
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.130
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.728
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 7.937
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.611
After features/support/hooks.rb:331 0.348
After features/support/hooks.rb:100 0.006
Tags: @product
2:10.337
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.514
And I log in to a new session 11.950
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.748
And I plug USB drive "to_upgrade" 2.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.264
Then the running Tails is installed on USB drive "to_upgrade" 15.340
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:331 3.753
After features/support/hooks.rb:100 0.000
Tags: @product
1:4.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.547
Then all tps features from the old Tails version are active 0.853
And Tails is running from USB drive "to_upgrade" 0.207
And the boot device has safe access rights 2.311
And the expected persistent files created with the old Tails version are present in the filesystem 1.015
And all persistent directories from the old Tails version have safe access rights 1.947
After features/support/hooks.rb:331 0.785
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:31.890
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.140
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.016
And Tor is ready 13.290
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.499
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.364
Given I shutdown Tails and wait for the computer to power off 9.250
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.624
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.066
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.035
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.181
When the network is plugged 0.014
And Tor is ready 9.595
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.044
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.669
Given I shutdown Tails and wait for the computer to power off 7.863
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.408
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.095
And the file system changes introduced in version 6.3~testoverlayfs are present 0.402
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.179
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.015
And Tor is ready 9.671
Then the Upgrader considers the system as up-to-date 10.499
# 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.116
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.337
After features/support/hooks.rb:331 0.887
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
19.215
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.461
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.700
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.687
After features/support/hooks.rb:331 1.000
After features/support/hooks.rb:100 0.000