Project Number Date
test_Tails_ISO_devel 4200 30 Jan 2026, 16:03

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:32.764 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:7.164
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 15.433
When I start Tails from USB drive "old" with network unplugged 47.258
Then the boot device has safe access rights 2.695
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.159
After features/support/hooks.rb:331 1.249
After features/support/hooks.rb:100 0.007
Tags: @product
1:32.516
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 57.518
Then Tails is running from USB drive "old" 0.241
And I create a persistent partition 25.841
And I take note of which tps features are available 0.831
Then a Tails persistence partition exists on USB drive "old" 0.940
And I shutdown Tails and wait for the computer to power off 7.070
After features/support/hooks.rb:331 0.405
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.640
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.383
Then Tails is running from USB drive "old" 0.250
And all tps features are active 1.343
When I write some files expected to persist 1.298
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 2.240
And I take note of which tps features are available 0.263
And I shutdown Tails and wait for the computer to power off 7.151
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.090
After features/support/hooks.rb:331 0.223
After features/support/hooks.rb:100 0.008
Tags: @product
2:19.301
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.577
And I log in to a new session 14.205
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.882
And I plug USB drive "to_upgrade" 2.319
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.082
Then the running Tails is installed on USB drive "to_upgrade" 17.877
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:331 10.084
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.204
Then all tps features from the old Tails version are active 1.325
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 3.053
And the expected persistent files created with the old Tails version are present in the filesystem 1.413
And all persistent directories from the old Tails version have safe access rights 2.511
After features/support/hooks.rb:331 0.908
After features/support/hooks.rb:100 0.017
4:19.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.396
And no SquashFS delta is installed 0.051
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.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.210
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.318
When the network is plugged 0.022
And Tor is ready 13.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.982
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.897
Given I shutdown Tails and wait for the computer to power off 16.791
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.905
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.327
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.257
When the network is plugged 0.040
And Tor is ready 10.539
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.637
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.353
Given I shutdown Tails and wait for the computer to power off 8.338
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.260
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 1.438
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.014
And Tor is ready 11.256
Then the Upgrader considers the system as up-to-date 10.690
# 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 5.083
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.390
After features/support/hooks.rb:331 0.798
After features/support/hooks.rb:100 0.011
22.482
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.820
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
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.022
And Tor is ready 11.187
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.071
After features/support/hooks.rb:331 0.734
After features/support/hooks.rb:100 0.000