Project Number Date
test_Tails_ISO_stable 6603 23 Aug 2026, 11:34

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:14.119 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:13.938
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 13.425
When I start Tails from USB drive "old" with network unplugged 56.628
Then the boot device has safe access rights 2.099
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.595
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.357
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login 47.088
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 22.979
And I take note of which tps features are available 6.743
Then a Tails persistence partition exists on USB drive "old" 0.565
And I shutdown Tails and wait for the computer to power off 2.643
After features/support/hooks.rb:339 0.502
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.002
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.784
Then Tails is running from USB drive "old" 0.192
And all tps features are active 6.538
When I write some files expected to persist 1.156
# 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.234
And all persistent directories from the old Tails version have safe access rights 1.953
And I take note of which tps features are available 6.209
And I shutdown Tails and wait for the computer to power off 2.570
# 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.134
After features/support/hooks.rb:339 0.271
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.163
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.354
And I log in to a new session 12.768
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.598
And I plug USB drive "to_upgrade" 2.299
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.967
Then the running Tails is installed on USB drive "to_upgrade" 17.921
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 1.616
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.225
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.917
Then all tps features from the old Tails version are active 1.220
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.082
And the expected persistent files created with the old Tails version are present in the filesystem 1.153
And all persistent directories from the old Tails version have safe access rights 1.543
After features/support/hooks.rb:339 0.920
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:30.042
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.140
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.306
When the network is plugged 0.032
And Tor is ready 13.040
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.986
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.335
Given I shutdown Tails and wait for the computer to power off 5.245
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.320
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.032
And the file system changes introduced in version 6.2~testoverlayfs are present 0.171
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.080
# 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.168
When the network is plugged 0.029
And Tor is ready 10.729
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.010
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.908
Given I shutdown Tails and wait for the computer to power off 2.603
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.285
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.745
And the file system changes introduced in version 6.3~testoverlayfs are present 0.306
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.036
And Tor is ready 10.665
Then the Upgrader considers the system as up-to-date 0.093
# 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.401
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.329
After features/support/hooks.rb:339 0.833
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
19.389
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.867
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 9.701
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.436
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.000