Project Number Date
test_Tails_ISO_devel 4257 27 Feb 2026, 09:06

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 15:8.158 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:35.671
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.123
When I start Tails from USB drive "old" with network unplugged 1:0.012
Then the boot device has safe access rights 3.418
And Tails is running from USB drive "old" 0.291
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.233
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:331 3.589
After features/support/hooks.rb:100 0.011
Tags: @product
1:42.451
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login 1:2.512
Then Tails is running from USB drive "old" 0.686
And I create a persistent partition 28.944
And I take note of which tps features are available 1.164
Then a Tails persistence partition exists on USB drive "old" 0.689
And I shutdown Tails and wait for the computer to power off 8.294
After features/support/hooks.rb:331 0.566
After features/support/hooks.rb:100 0.008
Tags: @product
1:44.691
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:15.959
Then Tails is running from USB drive "old" 0.679
And all tps features are active 1.931
When I write some files expected to persist 1.491
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.287
And all persistence configuration files have safe access rights 0.557
And all persistent directories from the old Tails version have safe access rights 2.156
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 3.107
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.881
After features/support/hooks.rb:331 0.166
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.878
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 10.600
And I log in to a new session 12.160
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.378
And I plug USB drive "to_upgrade" 2.716
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:58.921
Then the running Tails is installed on USB drive "to_upgrade" 20.430
And I unplug USB drive "to_upgrade" 0.297
And I unplug USB drive "__internal" 0.371
After features/support/hooks.rb:331 2.280
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.104
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.227
Then all tps features from the old Tails version are active 1.337
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.328
And the expected persistent files created with the old Tails version are present in the filesystem 1.411
And all persistent directories from the old Tails version have safe access rights 2.272
After features/support/hooks.rb:331 0.807
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
5:21.843
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 with a persistent partition enabled and logged in 11.712
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.398
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.075
And Tor is ready 25.060
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.636
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.789
Given I shutdown Tails and wait for the computer to power off 21.606
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:27.986
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.435
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.162
# 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.270
When the network is plugged 0.056
And Tor is ready 21.036
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.647
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.460
Given I shutdown Tails and wait for the computer to power off 17.021
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.170
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.043
And the file system changes introduced in version 6.3~testoverlayfs are present 0.638
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.202
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.057
And Tor is ready 22.156
Then the Upgrader considers the system as up-to-date 0.118
# 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.780
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.562
After features/support/hooks.rb:331 0.910
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
32.517
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 with a persistent partition enabled and logged in 10.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.385
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.059
And Tor is ready 21.140
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.684
After features/support/hooks.rb:331 1.134
After features/support/hooks.rb:100 0.000