Project Number Date
test_Tails_ISO_devel 4597 05 Sep 2026, 11:12

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:23.278 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:1.914
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.104
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.247
When I start Tails from USB drive "old" with network unplugged 44.630
Then the boot device has safe access rights 2.312
And Tails is running from USB drive "old" 0.182
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 1.611
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.958
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 47.946
Then Tails is running from USB drive "old" 0.210
And I create a persistent partition 24.642
And I take note of which tps features are available 7.284
Then a Tails persistence partition exists on USB drive "old" 0.562
And I shutdown Tails and wait for the computer to power off 4.229
After features/support/hooks.rb:339 0.430
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.126
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.236
Then Tails is running from USB drive "old" 0.235
And all tps features are active 7.664
When I write some files expected to persist 1.295
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.244
And all persistent directories from the old Tails version have safe access rights 2.035
And I take note of which tps features are available 6.285
And I shutdown Tails and wait for the computer to power off 2.565
# 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.293
After features/support/hooks.rb:339 0.226
After features/support/hooks.rb:108 0.013
Tags: @product
2:13.638
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.505
And I log in to a new session 11.940
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.643
And I plug USB drive "to_upgrade" 2.212
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.448
Then the running Tails is installed on USB drive "to_upgrade" 18.656
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.768
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.725
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.182
Then all tps features from the old Tails version are active 1.226
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.432
And the expected persistent files created with the old Tails version are present in the filesystem 0.980
And all persistent directories from the old Tails version have safe access rights 1.573
After features/support/hooks.rb:339 0.913
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:37.616
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 8.443
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.298
When the network is plugged 0.027
And Tor is ready 12.436
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.170
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.689
Given I shutdown Tails and wait for the computer to power off 5.425
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.470
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.474
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# 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.221
When the network is plugged 0.031
And Tor is ready 10.410
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.952
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.828
Given I shutdown Tails and wait for the computer to power off 3.906
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.533
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.351
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.164
When the network is plugged 0.030
And Tor is ready 11.007
Then the Upgrader considers the system as up-to-date 0.119
# 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.582
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.298
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 8.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
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.044
And Tor is ready 8.948
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.888
After features/support/hooks.rb:339 0.843
After features/support/hooks.rb:108 0.000