Project Number Date
test_Tails_ISO_stable 6510 18 Jul 2026, 11:41

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:56.808 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:3.698
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.701
When I start Tails from USB drive "old" with network unplugged 45.391
Then the boot device has safe access rights 2.815
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:339 1.253
After features/support/hooks.rb:108 0.007
Tags: @product
1:27.328
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 54.463
Then Tails is running from USB drive "old" 0.285
And I create a persistent partition 24.709
And I take note of which tps features are available 4.198
Then a Tails persistence partition exists on USB drive "old" 0.541
And I shutdown Tails and wait for the computer to power off 3.072
After features/support/hooks.rb:339 0.741
After features/support/hooks.rb:108 0.007
Tags: @product
1:40.745
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.102
Then Tails is running from USB drive "old" 0.300
And all tps features are active 5.136
When I write some files expected to persist 1.325
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 2.062
And I take note of which tps features are available 4.501
And I shutdown Tails and wait for the computer to power off 8.262
# 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.459
After features/support/hooks.rb:339 0.191
After features/support/hooks.rb:108 0.007
Tags: @product
2:10.671
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 7.802
And I log in to a new session 12.126
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.866
And I plug USB drive "to_upgrade" 2.273
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.476
Then the running Tails is installed on USB drive "to_upgrade" 15.845
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 0.787
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.269
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.707
Then all tps features from the old Tails version are active 1.205
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.605
And the expected persistent files created with the old Tails version are present in the filesystem 1.221
And all persistent directories from the old Tails version have safe access rights 2.214
After features/support/hooks.rb:339 0.513
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:58.365
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.959
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.663
When the network is plugged 0.024
And Tor is ready 12.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.344
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.345
Given I shutdown Tails and wait for the computer to power off 9.772
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.082
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.772
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# 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.263
When the network is plugged 0.025
And Tor is ready 9.647
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.443
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.672
Given I shutdown Tails and wait for the computer to power off 8.278
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.003
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.469
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.013
And Tor is ready 9.860
Then the Upgrader considers the system as up-to-date 10.619
# 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.318
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:339 1.043
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.729
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.320
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
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.017
And Tor is ready 10.413
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.676
After features/support/hooks.rb:339 0.982
After features/support/hooks.rb:108 0.000