Project Number Date
test_Tails_ISO_stable 6584 17 Aug 2026, 17:35

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:42.340 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:4.832
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.028
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.786
When I start Tails from USB drive "old" with network unplugged 46.842
Then the boot device has safe access rights 2.362
And Tails is running from USB drive "old" 0.272
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.703
After features/support/hooks.rb:108 0.043
Tags: @product
1:28.129
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login 50.855
Then Tails is running from USB drive "old" 0.190
And I create a persistent partition 24.641
And I take note of which tps features are available 7.812
Then a Tails persistence partition exists on USB drive "old" 0.598
And I shutdown Tails and wait for the computer to power off 3.928
After features/support/hooks.rb:339 0.232
After features/support/hooks.rb:108 0.005
Tags: @product
1:39.236
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.891
Then Tails is running from USB drive "old" 0.219
And all tps features are active 8.335
When I write some files expected to persist 1.333
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
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.977
And I take note of which tps features are available 6.801
And I shutdown Tails and wait for the computer to power off 3.973
# 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.180
After features/support/hooks.rb:339 0.101
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.287
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.248
And I log in to a new session 12.770
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.640
And I plug USB drive "to_upgrade" 2.199
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.382
Then the running Tails is installed on USB drive "to_upgrade" 18.795
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 1.773
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.603
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.126
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.295
Then all tps features from the old Tails version are active 1.076
And Tails is running from USB drive "to_upgrade" 0.217
And the boot device has safe access rights 2.112
And the expected persistent files created with the old Tails version are present in the filesystem 0.921
And all persistent directories from the old Tails version have safe access rights 1.853
After features/support/hooks.rb:339 0.594
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
3:43.123
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.536
And no SquashFS delta is installed 0.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.314
When the network is plugged 0.030
And Tor is ready 13.748
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.872
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.155
Given I shutdown Tails and wait for the computer to power off 5.362
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.691
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.133
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# 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.195
When the network is plugged 0.029
And Tor is ready 11.120
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.924
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.810
Given I shutdown Tails and wait for the computer to power off 4.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.980
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.451
And the file system changes introduced in version 6.3~testoverlayfs are present 0.401
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.095
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.152
When the network is plugged 0.030
And Tor is ready 10.413
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 3.905
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.380
After features/support/hooks.rb:339 0.817
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
21.126
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.023
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 10.795
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.917
After features/support/hooks.rb:339 0.607
After features/support/hooks.rb:108 0.000