Project Number Date
test_Tails_ISO_devel 4648 30 Sep 2026, 18:11

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:42.596 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:17.814
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.709
When I start Tails from USB drive "old" with network unplugged 59.812
Then the boot device has safe access rights 2.510
And Tails is running from USB drive "old" 0.187
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 3.722
After features/support/hooks.rb:108 0.051
Tags: @product
1:21.744
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 48.769
Then Tails is running from USB drive "old" 0.266
And I create a persistent partition 22.876
And I take note of which tps features are available 6.584
Then a Tails persistence partition exists on USB drive "old" 0.537
And I shutdown Tails and wait for the computer to power off 2.626
After features/support/hooks.rb:339 0.594
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.497
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.486
Then Tails is running from USB drive "old" 0.182
And all tps features are active 8.022
When I write some files expected to persist 1.085
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.250
And all persistent directories from the old Tails version have safe access rights 1.709
And I take note of which tps features are available 6.104
And I shutdown Tails and wait for the computer to power off 2.545
# 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.833
After features/support/hooks.rb:339 0.320
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.231
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 without a persistent partition and stopped at Tails Greeter's login screen 8.363
And I log in to a new session 11.921
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.724
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.166
Then the running Tails is installed on USB drive "to_upgrade" 19.570
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.149
After features/support/hooks.rb:339 2.104
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.212
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.883
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.348
Then all tps features from the old Tails version are active 1.205
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.460
And the expected persistent files created with the old Tails version are present in the filesystem 1.158
And all persistent directories from the old Tails version have safe access rights 1.935
After features/support/hooks.rb:339 0.511
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:40.231
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.689
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.190
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.380
When the network is plugged 0.030
And Tor is ready 13.756
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.997
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.172
Given I shutdown Tails and wait for the computer to power off 5.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.688
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 7.810
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.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.104
# 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.144
When the network is plugged 0.021
And Tor is ready 10.569
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.350
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.667
Given I shutdown Tails and wait for the computer to power off 2.609
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.557
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.221
And the file system changes introduced in version 6.3~testoverlayfs are present 0.344
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.035
And Tor is ready 10.295
Then the Upgrader considers the system as up-to-date 0.092
# 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.796
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.345
After features/support/hooks.rb:339 0.681
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
18.863
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.336
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 8.642
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.519
After features/support/hooks.rb:339 0.847
After features/support/hooks.rb:108 0.000