Project Number Date
test_Tails_ISO_devel 4432 04 Jun 2026, 16:14

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:33.350 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:7.839
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.086
When I start Tails from USB drive "old" with network unplugged 48.972
Then the boot device has safe access rights 2.752
And Tails is running from USB drive "old" 0.290
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.369
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:335 1.766
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.684
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 54.248
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 26.042
And I take note of which tps features are available 0.379
Then a Tails persistence partition exists on USB drive "old" 0.627
And I shutdown Tails and wait for the computer to power off 7.035
After features/support/hooks.rb:335 0.165
After features/support/hooks.rb:104 0.007
Tags: @product
1:28.207
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.272
Then Tails is running from USB drive "old" 0.322
And all tps features are active 1.211
When I write some files expected to persist 1.299
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 2.101
And I take note of which tps features are available 0.200
And I shutdown Tails and wait for the computer to power off 7.141
# 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.042
After features/support/hooks.rb:335 0.092
After features/support/hooks.rb:104 0.008
Tags: @product
2:13.046
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.997
And I log in to a new session 12.871
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.890
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.904
Then the running Tails is installed on USB drive "to_upgrade" 15.860
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:335 2.074
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.063
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.215
Then all tps features from the old Tails version are active 1.022
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.873
And the expected persistent files created with the old Tails version are present in the filesystem 1.291
And all persistent directories from the old Tails version have safe access rights 2.347
After features/support/hooks.rb:335 0.702
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:44.762
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.628
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.380
When the network is plugged 0.016
And Tor is ready 13.189
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.916
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.867
Given I shutdown Tails and wait for the computer to power off 9.605
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.365
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.298
And the file system changes introduced in version 6.2~testoverlayfs are present 0.238
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.152
# 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.184
When the network is plugged 0.015
And Tor is ready 11.486
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.826
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.395
Given I shutdown Tails and wait for the computer to power off 7.965
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.449
Then Tails is running version 6.3~testoverlayfs 0.029
And all tps features are active 1.302
And the file system changes introduced in version 6.3~testoverlayfs are present 0.409
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.015
And Tor is ready 11.588
Then the Upgrader considers the system as up-to-date 10.655
# 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.265
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.388
After features/support/hooks.rb:335 0.779
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
20.745
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.417
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
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.020
And Tor is ready 10.246
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.650
After features/support/hooks.rb:335 0.968
After features/support/hooks.rb:104 0.000