Project Number Date
test_Tails_ISO_devel 4286 20 Mar 2026, 14: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:31.310 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:1.989
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.025
When I start Tails from USB drive "old" with network unplugged 43.447
Then the boot device has safe access rights 2.673
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.244
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:331 3.609
After features/support/hooks.rb:100 0.029
Tags: @product
1:24.128
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 "old" with network unplugged and I login 54.492
Then Tails is running from USB drive "old" 0.282
And I create a persistent partition 23.927
And I take note of which tps features are available 0.725
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 4.116
After features/support/hooks.rb:331 0.262
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.469
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.868
Then Tails is running from USB drive "old" 0.280
And all tps features are active 1.488
When I write some files expected to persist 1.337
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.495
And all persistent directories from the old Tails version have safe access rights 2.004
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 7.976
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.610
After features/support/hooks.rb:331 0.361
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.638
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 7.820
And I log in to a new session 13.396
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.818
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.971
Then the running Tails is installed on USB drive "to_upgrade" 16.093
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 1.396
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.020
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.355
Then all tps features from the old Tails version are active 0.910
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.494
And the expected persistent files created with the old Tails version are present in the filesystem 1.061
And all persistent directories from the old Tails version have safe access rights 1.857
After features/support/hooks.rb:331 0.703
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:48.555
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.886
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.205
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.339
When the network is plugged 0.016
And Tor is ready 21.377
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.396
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.941
Given I shutdown Tails and wait for the computer to power off 19.630
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.073
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.094
And the file system changes introduced in version 6.2~testoverlayfs are present 0.188
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.194
When the network is plugged 0.014
And Tor is ready 20.210
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.274
Given I shutdown Tails and wait for the computer to power off 18.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.824
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.050
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.181
When the network is plugged 0.016
And Tor is ready 41.049
Then the Upgrader considers the system as up-to-date 0.117
# 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.100
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.471
After features/support/hooks.rb:331 0.938
After features/support/hooks.rb:100 0.040
Tags: @product @automatic_upgrade
25.508
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 7.454
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 17.332
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.347
After features/support/hooks.rb:331 0.718
After features/support/hooks.rb:100 0.000