Project Number Date
test_Tails_ISO_stable 6336 29 Apr 2026, 15:42

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:33.511 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:5.548
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.385
When I start Tails from USB drive "old" with network unplugged 45.950
Then the boot device has safe access rights 3.350
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.224
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:331 1.445
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.252
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 54.757
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 23.992
And I take note of which tps features are available 0.700
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 7.897
After features/support/hooks.rb:331 0.605
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.863
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.309
Then Tails is running from USB drive "old" 0.232
And all tps features are active 1.038
When I write some files expected to persist 1.259
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.142
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 1.991
And I take note of which tps features are available 0.168
And I shutdown Tails and wait for the computer to power off 7.931
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.336
After features/support/hooks.rb:331 0.497
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.964
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 without a persistent partition and stopped at Tails Greeter's login screen 7.712
And I log in to a new session 17.686
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.714
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.232
Then the running Tails is installed on USB drive "to_upgrade" 16.102
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 8.446
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.417
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.873
Then all tps features from the old Tails version are active 0.967
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.414
And the expected persistent files created with the old Tails version are present in the filesystem 1.028
And all persistent directories from the old Tails version have safe access rights 1.821
After features/support/hooks.rb:331 0.845
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:35.858
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 8.391
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.329
When the network is plugged 0.017
And Tor is ready 24.778
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.103
Given I shutdown Tails and wait for the computer to power off 20.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.802
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.052
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.175
When the network is plugged 0.014
And Tor is ready 20.549
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.359
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.754
Given I shutdown Tails and wait for the computer to power off 17.037
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.630
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.150
And the file system changes introduced in version 6.3~testoverlayfs are present 0.375
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.014
And Tor is ready 21.377
Then the Upgrader considers the system as up-to-date 0.111
# 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.142
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.367
After features/support/hooks.rb:331 0.658
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
30.606
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.575
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
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.019
And Tor is ready 22.325
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.355
After features/support/hooks.rb:331 0.580
After features/support/hooks.rb:100 0.000