Project Number Date
test_Tails_ISO_stable 6349 04 May 2026, 14:01

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:47.583 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:14.439
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 14.164
When I start Tails from USB drive "old" with network unplugged 55.455
Then the boot device has safe access rights 2.992
And Tails is running from USB drive "old" 0.257
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 3.670
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.085
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 58.474
Then Tails is running from USB drive "old" 0.284
And I create a persistent partition 25.604
And I take note of which tps features are available 0.755
Then a Tails persistence partition exists on USB drive "old" 0.569
And I shutdown Tails and wait for the computer to power off 4.334
After features/support/hooks.rb:331 0.328
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.526
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.889
Then Tails is running from USB drive "old" 0.286
And all tps features are active 1.327
When I write some files expected to persist 1.342
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.461
And all persistent directories from the old Tails version have safe access rights 1.952
And I take note of which tps features are available 0.174
And I shutdown Tails and wait for the computer to power off 8.247
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.591
After features/support/hooks.rb:331 0.308
After features/support/hooks.rb:100 0.006
Tags: @product
2:15.106
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.878
And I log in to a new session 13.999
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.825
And I plug USB drive "to_upgrade" 2.323
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.154
Then the running Tails is installed on USB drive "to_upgrade" 17.634
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:331 2.168
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.216
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.061
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.788
Then all tps features from the old Tails version are active 1.009
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.543
And the expected persistent files created with the old Tails version are present in the filesystem 1.430
And all persistent directories from the old Tails version have safe access rights 2.132
After features/support/hooks.rb:331 0.493
After features/support/hooks.rb:100 0.006
4:40.533
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 21.443
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
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.591
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.440
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.667
Given I shutdown Tails and wait for the computer to power off 6.820
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.278
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.192
When the network is plugged 0.017
And Tor is ready 20.812
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.356
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.503
Given I shutdown Tails and wait for the computer to power off 17.409
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.191
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.140
And the file system changes introduced in version 6.3~testoverlayfs are present 0.409
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.174
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.017
And Tor is ready 20.795
Then the Upgrader considers the system as up-to-date 0.108
# 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.806
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.464
After features/support/hooks.rb:331 0.923
After features/support/hooks.rb:100 0.025
25.675
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.658
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.053
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 17.324
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.357
After features/support/hooks.rb:331 0.528
After features/support/hooks.rb:100 0.000