Project Number Date
test_Tails_ISO_stable 6737 12 Oct 2026, 12:05

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:7.289 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:4.729
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.111
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.250
When I start Tails from USB drive "old" with network unplugged 46.511
Then the boot device has safe access rights 2.081
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.168
After features/support/hooks.rb:339 3.802
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.042
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 50.905
Then Tails is running from USB drive "old" 0.224
And I create a persistent partition 23.815
And I take note of which tps features are available 6.966
Then a Tails persistence partition exists on USB drive "old" 0.592
And I shutdown Tails and wait for the computer to power off 4.450
After features/support/hooks.rb:339 0.246
After features/support/hooks.rb:108 0.005
Tags: @product
1:38.786
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.890
Then Tails is running from USB drive "old" 0.187
And all tps features are active 7.796
When I write some files expected to persist 1.310
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.140
And all persistence configuration files have safe access rights 0.262
And all persistent directories from the old Tails version have safe access rights 1.845
And I take note of which tps features are available 6.826
And I shutdown Tails and wait for the computer to power off 2.530
# 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.897
After features/support/hooks.rb:339 0.566
After features/support/hooks.rb:108 0.005
Tags: @product
2:15.250
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 8.762
And I log in to a new session 12.728
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.087
And I plug USB drive "to_upgrade" 2.284
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.240
Then the running Tails is installed on USB drive "to_upgrade" 18.881
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 1.911
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.881
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.145
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.256
Then all tps features from the old Tails version are active 1.258
And Tails is running from USB drive "to_upgrade" 0.257
And the boot device has safe access rights 2.278
And the expected persistent files created with the old Tails version are present in the filesystem 1.030
And all persistent directories from the old Tails version have safe access rights 1.653
After features/support/hooks.rb:339 0.839
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
4:8.421
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 21.684
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
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.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.027
And Tor is ready 13.687
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.304
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.179
Given I shutdown Tails and wait for the computer to power off 5.614
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.529
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 10.186
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.036
And Tor is ready 9.890
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.356
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.801
Given I shutdown Tails and wait for the computer to power off 4.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.144
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 12.989
And the file system changes introduced in version 6.3~testoverlayfs are present 0.368
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.205
When the network is plugged 0.033
And Tor is ready 10.798
Then the Upgrader considers the system as up-to-date 0.136
# 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.644
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.392
After features/support/hooks.rb:339 1.062
After features/support/hooks.rb:108 0.045
Tags: @product @automatic_upgrade
21.178
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 9.188
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
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.061
And Tor is ready 10.507
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.035
After features/support/hooks.rb:339 1.074
After features/support/hooks.rb:108 0.000