Project Number Date
test_Tails_ISO_stable 6570 10 Aug 2026, 12:47

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 11:56.007 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:12.791
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.114
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.421
When I start Tails from USB drive "old" with network unplugged 53.961
Then the boot device has safe access rights 2.490
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.246
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:339 3.802
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.310
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 51.373
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 25.205
And I take note of which tps features are available 6.795
Then a Tails persistence partition exists on USB drive "old" 0.629
And I shutdown Tails and wait for the computer to power off 3.933
After features/support/hooks.rb:339 0.510
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.953
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.126
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.054
Then Tails is running from USB drive "old" 0.307
And all tps features are active 7.925
When I write some files expected to persist 1.143
# 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.264
And all persistent directories from the old Tails version have safe access rights 1.710
And I take note of which tps features are available 6.730
And I shutdown Tails and wait for the computer to power off 2.617
# 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" 11.888
After features/support/hooks.rb:339 0.422
After features/support/hooks.rb:108 0.006
Tags: @product
2:19.023
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.621
And I log in to a new session 13.189
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.710
And I plug USB drive "to_upgrade" 2.302
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.219
Then the running Tails is installed on USB drive "to_upgrade" 20.710
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:339 1.811
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.175
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.971
Then all tps features from the old Tails version are active 1.252
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.618
And the expected persistent files created with the old Tails version are present in the filesystem 1.114
And all persistent directories from the old Tails version have safe access rights 1.896
After features/support/hooks.rb:339 0.540
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:45.039
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 8.594
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.570
When the network is plugged 0.055
And Tor is ready 12.232
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.094
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.128
Given I shutdown Tails and wait for the computer to power off 5.613
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.449
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 9.033
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.122
# 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.223
When the network is plugged 0.025
And Tor is ready 10.878
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.988
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.188
Given I shutdown Tails and wait for the computer to power off 4.428
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.518
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.470
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.036
And Tor is ready 10.661
Then the Upgrader considers the system as up-to-date 0.120
# 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.301
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.439
After features/support/hooks.rb:339 1.139
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.714
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.944
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
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.037
And Tor is ready 8.568
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.833
After features/support/hooks.rb:339 0.982
After features/support/hooks.rb:108 0.000