Project Number Date
test_Tails_ISO_devel 4553 17 Aug 2026, 17:54

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:32.061 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.935
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.116
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.663
When I start Tails from USB drive "old" with network unplugged 46.056
Then the boot device has safe access rights 2.371
And Tails is running from USB drive "old" 0.260
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 3.641
After features/support/hooks.rb:108 0.017
Tags: @product
1:25.863
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login 49.450
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 24.375
And I take note of which tps features are available 7.056
Then a Tails persistence partition exists on USB drive "old" 0.559
And I shutdown Tails and wait for the computer to power off 4.074
After features/support/hooks.rb:339 0.516
After features/support/hooks.rb:108 0.005
Tags: @product
1:38.884
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 with persistence enabled 1:6.272
Then Tails is running from USB drive "old" 0.243
And all tps features are active 8.089
When I write some files expected to persist 1.224
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 1.798
And I take note of which tps features are available 6.214
And I shutdown Tails and wait for the computer to power off 2.610
# 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.839
After features/support/hooks.rb:339 0.446
After features/support/hooks.rb:108 0.005
Tags: @product
2:15.302
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 8.319
And I log in to a new session 13.557
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.844
And I plug USB drive "to_upgrade" 2.196
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.175
Then the running Tails is installed on USB drive "to_upgrade" 18.915
And I unplug USB drive "to_upgrade" 0.165
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.946
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.284
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.958
Then all tps features from the old Tails version are active 1.053
And Tails is running from USB drive "to_upgrade" 0.196
And the boot device has safe access rights 2.227
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.743
After features/support/hooks.rb:339 0.967
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:39.140
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.020
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.184
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.398
When the network is plugged 0.032
And Tor is ready 13.480
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.360
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.587
Given I shutdown Tails and wait for the computer to power off 5.344
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.718
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 8.640
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.199
When the network is plugged 0.034
And Tor is ready 10.544
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.706
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.964
Given I shutdown Tails and wait for the computer to power off 2.646
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.070
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 8.338
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.030
And Tor is ready 11.131
Then the Upgrader considers the system as up-to-date 0.146
# 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.509
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.317
After features/support/hooks.rb:339 0.785
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.650
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 8.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.879
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.318
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.000