Project Number Date
test_Tails_ISO_stable 6304 15 Apr 2026, 13:01

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:44.391 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.257
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.222
When I start Tails from USB drive "old" with network unplugged 51.526
Then the boot device has safe access rights 2.707
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:331 1.376
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.884
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 53.379
Then Tails is running from USB drive "old" 0.261
And I create a persistent partition 24.163
And I take note of which tps features are available 0.727
Then a Tails persistence partition exists on USB drive "old" 0.603
And I shutdown Tails and wait for the computer to power off 6.692
After features/support/hooks.rb:331 0.430
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.131
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.075
Then Tails is running from USB drive "old" 0.222
And all tps features are active 1.438
When I write some files expected to persist 1.495
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.589
And all persistent directories from the old Tails version have safe access rights 2.131
And I take note of which tps features are available 0.219
And I shutdown Tails and wait for the computer to power off 2.707
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.970
After features/support/hooks.rb:331 0.351
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.353
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.192
And I log in to a new session 12.700
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.843
And I plug USB drive "to_upgrade" 2.320
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.739
Then the running Tails is installed on USB drive "to_upgrade" 16.288
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 2.044
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.071
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.854
Then all tps features from the old Tails version are active 1.030
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.788
And the expected persistent files created with the old Tails version are present in the filesystem 1.138
And all persistent directories from the old Tails version have safe access rights 1.968
After features/support/hooks.rb:331 0.711
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:59.111
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.333
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.190
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.021
And Tor is ready 42.669
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.413
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.252
Given I shutdown Tails and wait for the computer to power off 18.835
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.397
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.091
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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 20.822
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.400
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.360
Given I shutdown Tails and wait for the computer to power off 17.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.432
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.212
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.071
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.013
And Tor is ready 20.877
Then the Upgrader considers the system as up-to-date 0.112
# 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.823
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.470
After features/support/hooks.rb:331 0.875
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
26.581
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 with a persistent partition enabled and logged in 7.952
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 17.943
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
After features/support/hooks.rb:331 0.614
After features/support/hooks.rb:100 0.000