Project Number Date
test_Tails_ISO_stable 6249 31 Mar 2026, 07:02

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:23.542 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.076
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.768
When I start Tails from USB drive "old" with network unplugged 50.413
Then the boot device has safe access rights 2.999
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:331 1.459
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.981
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 54.640
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 24.522
And I take note of which tps features are available 0.666
Then a Tails persistence partition exists on USB drive "old" 0.633
And I shutdown Tails and wait for the computer to power off 8.208
After features/support/hooks.rb:331 0.430
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.540
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.671
Then Tails is running from USB drive "old" 0.308
And all tps features are active 1.337
When I write some files expected to persist 1.303
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.248
And I take note of which tps features are available 0.240
And I shutdown Tails and wait for the computer to power off 8.140
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.667
After features/support/hooks.rb:331 0.289
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.749
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 without a persistent partition and stopped at Tails Greeter's login screen 8.146
And I log in to a new session 12.979
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.829
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.488
Then the running Tails is installed on USB drive "to_upgrade" 15.640
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:331 2.502
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.284
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.027
Then all tps features from the old Tails version are active 1.049
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 2.660
And the expected persistent files created with the old Tails version are present in the filesystem 1.132
And all persistent directories from the old Tails version have safe access rights 2.033
After features/support/hooks.rb:331 0.959
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
4:27.745
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.355
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.018
And Tor is ready 21.491
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.399
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.356
Given I shutdown Tails and wait for the computer to power off 19.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.037
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.219
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.185
When the network is plugged 0.014
And Tor is ready 22.238
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.355
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.127
Given I shutdown Tails and wait for the computer to power off 4.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.196
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.141
And the file system changes introduced in version 6.3~testoverlayfs are present 0.359
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.018
And Tor is ready 21.093
Then the Upgrader considers the system as up-to-date 0.134
# 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 5.024
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.428
After features/support/hooks.rb:331 0.789
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
25.165
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.621
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 16.848
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.373
After features/support/hooks.rb:331 0.740
After features/support/hooks.rb:100 0.000