Project Number Date
test_Tails_ISO_stable 6524 22 Jul 2026, 13:05

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:3.235 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:9.045
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.371
When I start Tails from USB drive "old" with network unplugged 50.197
Then the boot device has safe access rights 2.669
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:339 1.254
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.562
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 53.269
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 24.333
And I take note of which tps features are available 4.379
Then a Tails persistence partition exists on USB drive "old" 0.560
And I shutdown Tails and wait for the computer to power off 6.742
After features/support/hooks.rb:339 0.369
After features/support/hooks.rb:108 0.007
Tags: @product
1:40.451
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.896
Then Tails is running from USB drive "old" 0.236
And all tps features are active 5.080
When I write some files expected to persist 1.356
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.292
And all persistent directories from the old Tails version have safe access rights 1.800
And I take note of which tps features are available 4.021
And I shutdown Tails and wait for the computer to power off 8.221
# 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" 12.312
After features/support/hooks.rb:339 0.384
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.174
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.259
And I log in to a new session 13.584
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.784
And I plug USB drive "to_upgrade" 2.251
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.304
Then the running Tails is installed on USB drive "to_upgrade" 16.702
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:339 2.108
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.242
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.946
Then all tps features from the old Tails version are active 1.080
And Tails is running from USB drive "to_upgrade" 0.226
And the boot device has safe access rights 2.701
And the expected persistent files created with the old Tails version are present in the filesystem 1.217
And all persistent directories from the old Tails version have safe access rights 1.992
After features/support/hooks.rb:339 1.210
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:55.272
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.238
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.013
And Tor is ready 16.306
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.967
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.892
Given I shutdown Tails and wait for the computer to power off 5.453
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.672
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.439
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.229
When the network is plugged 0.016
And Tor is ready 11.548
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.651
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.492
Given I shutdown Tails and wait for the computer to power off 4.090
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.415
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.975
And the file system changes introduced in version 6.3~testoverlayfs are present 0.415
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.014
And Tor is ready 9.514
Then the Upgrader considers the system as up-to-date 10.504
# 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.153
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.381
After features/support/hooks.rb:339 0.680
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
20.484
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.222
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 10.575
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.343
After features/support/hooks.rb:339 0.745
After features/support/hooks.rb:108 0.000