Project Number Date
test_Tails_ISO_stable 6685 21 Sep 2026, 11:35

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 10:59.145 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
56.223
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.366
When I start Tails from USB drive "old" with network unplugged 38.740
Then the boot device has safe access rights 2.383
And Tails is running from USB drive "old" 0.188
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 3.878
After features/support/hooks.rb:108 0.007
Tags: @product
1:23.943
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login 47.602
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 24.033
And I take note of which tps features are available 6.381
Then a Tails persistence partition exists on USB drive "old" 0.475
And I shutdown Tails and wait for the computer to power off 5.057
After features/support/hooks.rb:339 0.358
After features/support/hooks.rb:108 0.007
Tags: @product
1:32.459
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.773
Then Tails is running from USB drive "old" 0.183
And all tps features are active 7.704
When I write some files expected to persist 1.227
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.131
And all persistence configuration files have safe access rights 0.238
And all persistent directories from the old Tails version have safe access rights 1.711
And I take note of which tps features are available 5.928
And I shutdown Tails and wait for the computer to power off 2.505
# 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.952
After features/support/hooks.rb:339 0.339
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.104
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.218
And I log in to a new session 13.328
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.727
And I plug USB drive "to_upgrade" 2.193
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.710
Then the running Tails is installed on USB drive "to_upgrade" 16.672
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.828
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.483
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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:2.538
Then all tps features from the old Tails version are active 1.148
And Tails is running from USB drive "to_upgrade" 0.202
And the boot device has safe access rights 1.997
And the expected persistent files created with the old Tails version are present in the filesystem 0.874
And all persistent directories from the old Tails version have safe access rights 1.639
After features/support/hooks.rb:339 0.705
After features/support/hooks.rb:108 0.042
Tags: @product @automatic_upgrade
3:26.839
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.085
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
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.195
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.289
When the network is plugged 0.027
And Tor is ready 11.757
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.443
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.735
Given I shutdown Tails and wait for the computer to power off 5.430
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.107
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.902
And the file system changes introduced in version 6.2~testoverlayfs are present 0.192
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.196
When the network is plugged 0.036
And Tor is ready 10.458
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.899
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.757
Given I shutdown Tails and wait for the computer to power off 2.596
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.070
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.193
And the file system changes introduced in version 6.3~testoverlayfs are present 0.279
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.097
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.057
And Tor is ready 10.300
Then the Upgrader considers the system as up-to-date 0.079
# 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.575
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.319
After features/support/hooks.rb:339 1.003
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.092
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.096
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.054
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 8.530
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.099
After features/support/hooks.rb:339 0.553
After features/support/hooks.rb:108 0.000