Project Number Date
test_Tails_ISO_devel 4602 08 Sep 2026, 11:28

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:11.217 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:10.505
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.964
When I start Tails from USB drive "old" with network unplugged 51.955
Then the boot device has safe access rights 2.698
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:339 1.332
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.924
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login 52.513
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 23.468
And I take note of which tps features are available 7.150
Then a Tails persistence partition exists on USB drive "old" 0.529
And I shutdown Tails and wait for the computer to power off 3.904
After features/support/hooks.rb:339 0.400
After features/support/hooks.rb:108 0.007
Tags: @product
1:42.302
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.518
Then Tails is running from USB drive "old" 0.300
And all tps features are active 8.407
When I write some files expected to persist 1.302
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.361
And all persistent directories from the old Tails version have safe access rights 1.910
And I take note of which tps features are available 6.960
And I shutdown Tails and wait for the computer to power off 4.077
# 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.221
After features/support/hooks.rb:339 0.510
After features/support/hooks.rb:108 0.011
Tags: @product
2:16.618
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.649
And I log in to a new session 12.808
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.787
And I plug USB drive "to_upgrade" 2.247
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.405
Then the running Tails is installed on USB drive "to_upgrade" 19.489
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.605
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.284
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.920
Then all tps features from the old Tails version are active 1.170
And Tails is running from USB drive "to_upgrade" 0.302
And the boot device has safe access rights 2.649
And the expected persistent files created with the old Tails version are present in the filesystem 1.170
And all persistent directories from the old Tails version have safe access rights 1.997
After features/support/hooks.rb:339 0.913
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
4:3.515
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.420
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.361
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.021
And Tor is ready 12.950
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.609
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.525
Given I shutdown Tails and wait for the computer to power off 5.629
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.760
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 11.542
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.204
When the network is plugged 0.956
And Tor is ready 10.979
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.004
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.061
Given I shutdown Tails and wait for the computer to power off 4.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.501
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.189
And the file system changes introduced in version 6.3~testoverlayfs are present 0.337
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.066
And Tor is ready 11.302
Then the Upgrader considers the system as up-to-date 0.108
# 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.487
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.452
After features/support/hooks.rb:339 0.909
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
19.067
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 7.999
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 8.600
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.056
After features/support/hooks.rb:339 0.724
After features/support/hooks.rb:108 0.000