Project Number Date
test_Tails_ISO_devel 4460 18 Jun 2026, 16:16

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:13.002 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:9.684
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.133
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 13.757
When I start Tails from USB drive "old" with network unplugged 50.657
Then the boot device has safe access rights 3.247
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.262
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:339 1.559
After features/support/hooks.rb:108 0.021
Tags: @product
1:34.024
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.072
Given a computer 0.255
And I start Tails from USB drive "old" with network unplugged and I login 54.727
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 25.752
And I take note of which tps features are available 4.281
Then a Tails persistence partition exists on USB drive "old" 0.554
And I shutdown Tails and wait for the computer to power off 8.204
After features/support/hooks.rb:339 0.400
After features/support/hooks.rb:108 0.018
Tags: @product
1:37.480
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.120
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.243
Then Tails is running from USB drive "old" 0.271
And all tps features are active 5.492
When I write some files expected to persist 1.173
# 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.295
And all persistent directories from the old Tails version have safe access rights 2.080
And I take note of which tps features are available 3.887
And I shutdown Tails and wait for the computer to power off 4.483
# 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.261
After features/support/hooks.rb:339 0.369
After features/support/hooks.rb:108 0.019
Tags: @product
2:11.393
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.401
And I log in to a new session 11.991
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.836
And I plug USB drive "to_upgrade" 2.279
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.970
Then the running Tails is installed on USB drive "to_upgrade" 15.603
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:339 1.992
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.407
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.127
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.816
Then all tps features from the old Tails version are active 1.130
And Tails is running from USB drive "to_upgrade" 0.243
And the boot device has safe access rights 2.825
And the expected persistent files created with the old Tails version are present in the filesystem 1.182
And all persistent directories from the old Tails version have safe access rights 2.081
After features/support/hooks.rb:339 0.909
After features/support/hooks.rb:108 0.040
Tags: @product @automatic_upgrade
4:5.463
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.970
And no SquashFS delta is installed 0.080
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.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.344
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.373
When the network is plugged 0.016
And Tor is ready 13.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.061
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.570
Given I shutdown Tails and wait for the computer to power off 10.167
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.733
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.873
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.173
# 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.266
When the network is plugged 0.013
And Tor is ready 11.505
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.763
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.484
Given I shutdown Tails and wait for the computer to power off 8.661
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.700
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.894
And the file system changes introduced in version 6.3~testoverlayfs are present 0.399
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.016
And Tor is ready 10.160
Then the Upgrader considers the system as up-to-date 10.679
# 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.415
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.328
After features/support/hooks.rb:339 0.964
After features/support/hooks.rb:108 0.037
Tags: @product @automatic_upgrade
20.548
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.681
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.498
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.866
After features/support/hooks.rb:339 0.667
After features/support/hooks.rb:108 0.000