Project Number Date
test_Tails_ISO_stable 6301 14 Apr 2026, 19: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 13:5.742 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:11.890
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.772
When I start Tails from USB drive "old" with network unplugged 51.694
Then the boot device has safe access rights 3.319
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:331 1.678
After features/support/hooks.rb:100 0.009
Tags: @product
1:33.727
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login 58.787
Then Tails is running from USB drive "old" 0.572
And I create a persistent partition 25.689
And I take note of which tps features are available 0.786
Then a Tails persistence partition exists on USB drive "old" 0.669
And I shutdown Tails and wait for the computer to power off 7.135
After features/support/hooks.rb:331 0.144
After features/support/hooks.rb:100 0.008
Tags: @product
1:33.650
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.091
Then Tails is running from USB drive "old" 0.275
And all tps features are active 1.279
When I write some files expected to persist 1.252
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.212
And I take note of which tps features are available 0.193
And I shutdown Tails and wait for the computer to power off 8.455
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.203
After features/support/hooks.rb:331 0.179
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.854
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.992
And I log in to a new session 13.444
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.034
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.449
Then the running Tails is installed on USB drive "to_upgrade" 16.414
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 1.990
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.814
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.061
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.439
Then all tps features from the old Tails version are active 1.198
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 3.291
And the expected persistent files created with the old Tails version are present in the filesystem 1.401
And all persistent directories from the old Tails version have safe access rights 2.146
After features/support/hooks.rb:331 0.966
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:46.491
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.819
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
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.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.018
And Tor is ready 21.588
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.429
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.498
Given I shutdown Tails and wait for the computer to power off 19.571
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.222
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.294
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# 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.233
When the network is plugged 0.014
And Tor is ready 22.092
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.403
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.941
Given I shutdown Tails and wait for the computer to power off 12.416
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.356
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.107
And the file system changes introduced in version 6.3~testoverlayfs are present 0.389
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.166
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.019
And Tor is ready 21.740
Then the Upgrader considers the system as up-to-date 0.124
# 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.783
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:331 1.230
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
28.314
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.580
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 18.818
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.474
After features/support/hooks.rb:331 0.930
After features/support/hooks.rb:100 0.000