Project Number Date
test_Tails_ISO_stable 6598 19 Aug 2026, 19:55

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:38.653 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
55.933
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 12.771
When I start Tails from USB drive "old" with network unplugged 39.750
Then the boot device has safe access rights 1.714
And Tails is running from USB drive "old" 0.201
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.130
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 3.606
After features/support/hooks.rb:108 0.037
Tags: @product
1:17.970
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 47.164
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 21.994
And I take note of which tps features are available 5.503
Then a Tails persistence partition exists on USB drive "old" 0.440
And I shutdown Tails and wait for the computer to power off 2.588
After features/support/hooks.rb:339 0.347
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.984
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.472
Then Tails is running from USB drive "old" 0.188
And all tps features are active 6.886
When I write some files expected to persist 1.099
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.147
And all persistence configuration files have safe access rights 0.322
And all persistent directories from the old Tails version have safe access rights 1.539
And I take note of which tps features are available 5.592
And I shutdown Tails and wait for the computer to power off 2.511
# 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.143
After features/support/hooks.rb:339 0.283
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.709
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.084
And I log in to a new session 10.246
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.589
And I plug USB drive "to_upgrade" 2.187
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.595
Then the running Tails is installed on USB drive "to_upgrade" 17.748
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 6.477
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.307
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.118
Then all tps features from the old Tails version are active 1.113
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 2.244
And the expected persistent files created with the old Tails version are present in the filesystem 0.966
And all persistent directories from the old Tails version have safe access rights 1.518
After features/support/hooks.rb:339 0.907
After features/support/hooks.rb:108 0.006
3:22.396
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.249
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.029
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.391
When the network is plugged 0.034
And Tor is ready 12.160
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.474
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.253
Given I shutdown Tails and wait for the computer to power off 5.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.952
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.113
And the file system changes introduced in version 6.2~testoverlayfs are present 0.163
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.115
# 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.141
When the network is plugged 0.030
And Tor is ready 10.003
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.455
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.613
Given I shutdown Tails and wait for the computer to power off 3.930
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.952
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.470
And the file system changes introduced in version 6.3~testoverlayfs are present 0.300
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.090
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.033
And Tor is ready 10.064
Then the Upgrader considers the system as up-to-date 0.094
# 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 2.964
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.286
After features/support/hooks.rb:339 0.906
After features/support/hooks.rb:108 0.009
18.351
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.709
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 8.906
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.377
After features/support/hooks.rb:339 0.742
After features/support/hooks.rb:108 0.000