Project Number Date
test_Tails_ISO_devel 4589 03 Sep 2026, 11:09

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:9.830 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.982
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.461
When I start Tails from USB drive "old" with network unplugged 47.816
Then the boot device has safe access rights 1.949
And Tails is running from USB drive "old" 0.199
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 1.697
After features/support/hooks.rb:108 0.006
Tags: @product
1:20.987
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 47.589
Then Tails is running from USB drive "old" 0.158
And I create a persistent partition 22.542
And I take note of which tps features are available 6.163
Then a Tails persistence partition exists on USB drive "old" 0.507
And I shutdown Tails and wait for the computer to power off 3.954
After features/support/hooks.rb:339 0.320
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.282
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.047
Then Tails is running from USB drive "old" 0.344
And all tps features are active 7.553
When I write some files expected to persist 1.135
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.139
And all persistence configuration files have safe access rights 0.230
And all persistent directories from the old Tails version have safe access rights 1.661
And I take note of which tps features are available 5.955
And I shutdown Tails and wait for the computer to power off 2.551
# 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.579
After features/support/hooks.rb:339 0.524
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.932
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.753
And I log in to a new session 11.529
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.579
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.668
Then the running Tails is installed on USB drive "to_upgrade" 17.889
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 1.705
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.885
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.115
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.984
Then all tps features from the old Tails version are active 1.034
And Tails is running from USB drive "to_upgrade" 0.203
And the boot device has safe access rights 2.148
And the expected persistent files created with the old Tails version are present in the filesystem 0.801
And all persistent directories from the old Tails version have safe access rights 1.598
After features/support/hooks.rb:339 0.725
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:32.273
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.990
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.298
When the network is plugged 0.029
And Tor is ready 13.505
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.521
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.492
Given I shutdown Tails and wait for the computer to power off 5.419
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.444
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.242
And the file system changes introduced in version 6.2~testoverlayfs are present 0.212
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.111
# 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.163
When the network is plugged 0.031
And Tor is ready 10.363
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.927
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.400
Given I shutdown Tails and wait for the computer to power off 3.970
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.118
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.158
And the file system changes introduced in version 6.3~testoverlayfs are present 0.320
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.113
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.024
And Tor is ready 10.366
Then the Upgrader considers the system as up-to-date 0.075
# 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.678
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.322
After features/support/hooks.rb:339 0.986
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
19.486
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.741
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
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.052
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 9.775
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.635
After features/support/hooks.rb:339 0.654
After features/support/hooks.rb:108 0.000