Project Number Date
test_Tails_ISO_devel 4567 25 Aug 2026, 11:12

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 10:47.414 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
56.086
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.502
When I start Tails from USB drive "old" with network unplugged 38.540
Then the boot device has safe access rights 2.296
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 1.663
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.602
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 49.151
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 24.491
And I take note of which tps features are available 6.454
Then a Tails persistence partition exists on USB drive "old" 0.555
And I shutdown Tails and wait for the computer to power off 2.616
After features/support/hooks.rb:339 0.274
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.669
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.120
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.097
Then Tails is running from USB drive "old" 0.222
And all tps features are active 6.765
When I write some files expected to persist 1.033
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.135
And all persistence configuration files have safe access rights 0.221
And all persistent directories from the old Tails version have safe access rights 1.462
And I take note of which tps features are available 6.221
And I shutdown Tails and wait for the computer to power off 2.531
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 10.857
After features/support/hooks.rb:339 0.166
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.162
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.287
And I log in to a new session 11.228
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.676
And I plug USB drive "to_upgrade" 2.222
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.962
Then the running Tails is installed on USB drive "to_upgrade" 17.546
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 0.580
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.884
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.416
Then all tps features from the old Tails version are active 0.977
And Tails is running from USB drive "to_upgrade" 0.189
And the boot device has safe access rights 1.789
And the expected persistent files created with the old Tails version are present in the filesystem 0.820
And all persistent directories from the old Tails version have safe access rights 1.620
After features/support/hooks.rb:339 0.857
After features/support/hooks.rb:108 0.005
3:22.664
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.835
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
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.171
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.289
When the network is plugged 0.036
And Tor is ready 12.650
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.416
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.824
Given I shutdown Tails and wait for the computer to power off 5.223
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.032
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.727
And the file system changes introduced in version 6.2~testoverlayfs are present 0.157
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.103
# 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.161
When the network is plugged 0.031
And Tor is ready 10.160
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.366
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.350
Given I shutdown Tails and wait for the computer to power off 2.595
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.993
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.444
And the file system changes introduced in version 6.3~testoverlayfs are present 0.341
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.084
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.144
When the network is plugged 0.027
And Tor is ready 10.553
Then the Upgrader considers the system as up-to-date 0.090
# 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.116
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.347
After features/support/hooks.rb:339 0.609
After features/support/hooks.rb:108 0.009
19.344
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.044
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.041
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.039
And Tor is ready 9.556
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.393
After features/support/hooks.rb:339 0.820
After features/support/hooks.rb:108 0.000