Project Number Date
test_Tails_ISO_stable 6536 27 Jul 2026, 18:54

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:29.288 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:17.283
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.112
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.658
When I start Tails from USB drive "old" with network unplugged 57.998
Then the boot device has safe access rights 2.797
And Tails is running from USB drive "old" 0.216
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.365
After features/support/hooks.rb:108 0.007
Tags: @product
1:35.623
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 56.605
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 28.711
And I take note of which tps features are available 4.862
Then a Tails persistence partition exists on USB drive "old" 0.741
And I shutdown Tails and wait for the computer to power off 4.351
After features/support/hooks.rb:339 0.238
After features/support/hooks.rb:108 0.007
Tags: @product
1:39.354
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.992
Then Tails is running from USB drive "old" 0.247
And all tps features are active 5.963
When I write some files expected to persist 1.439
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.336
And all persistent directories from the old Tails version have safe access rights 1.778
And I take note of which tps features are available 4.156
And I shutdown Tails and wait for the computer to power off 4.108
# 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" 13.087
After features/support/hooks.rb:339 0.540
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.759
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 7.996
And I log in to a new session 14.708
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.779
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.294
Then the running Tails is installed on USB drive "to_upgrade" 16.461
And I unplug USB drive "to_upgrade" 0.161
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.188
After features/support/hooks.rb:108 0.000
Tags: @product
1:21.433
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.112
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.356
Then all tps features from the old Tails version are active 1.261
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 2.925
And the expected persistent files created with the old Tails version are present in the filesystem 1.313
And all persistent directories from the old Tails version have safe access rights 2.158
After features/support/hooks.rb:339 0.875
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
4:0.492
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.002
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.332
When the network is plugged 0.012
And Tor is ready 12.874
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.133
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.262
Given I shutdown Tails and wait for the computer to power off 8.410
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.111
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 5.900
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.232
When the network is plugged 0.017
And Tor is ready 11.197
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.917
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.671
Given I shutdown Tails and wait for the computer to power off 4.109
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.015
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 5.698
And the file system changes introduced in version 6.3~testoverlayfs are present 0.389
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.017
And Tor is ready 10.240
Then the Upgrader considers the system as up-to-date 10.618
# 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.447
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.358
After features/support/hooks.rb:339 0.940
After features/support/hooks.rb:108 0.053
Tags: @product @automatic_upgrade
20.341
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.466
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.446
After features/support/hooks.rb:339 0.868
After features/support/hooks.rb:108 0.000