Project Number Date
test_Tails_ISO_stable 5968 25 Nov 2025, 18:12

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 19:39.670 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:58.988
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 32.373
When I start Tails from USB drive "old" with network unplugged 1:21.433
Then the boot device has safe access rights 2.977
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.260
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:331 4.064
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.800
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:27.940
Then Tails is running from USB drive "old" 0.420
And I create a persistent partition 29.416
And I take note of which tps features are available 1.235
Then a Tails persistence partition exists on USB drive "old" 0.699
And I shutdown Tails and wait for the computer to power off 7.919
After features/support/hooks.rb:331 0.288
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.979
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.313
Then Tails is running from USB drive "old" 0.305
And all tps features are active 2.184
When I write some files expected to persist 1.925
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.476
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 7.882
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.491
After features/support/hooks.rb:331 0.430
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.124
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 13.221
And I log in to a new session 16.911
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.678
And I plug USB drive "to_upgrade" 3.085
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.698
Then the running Tails is installed on USB drive "to_upgrade" 20.091
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:331 3.966
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.446
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:39.041
Then all tps features from the old Tails version are active 1.539
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 4.555
And the expected persistent files created with the old Tails version are present in the filesystem 1.362
And all persistent directories from the old Tails version have safe access rights 3.440
After features/support/hooks.rb:331 2.690
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:12.860
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.345
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.053
And Tor is ready 34.541
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.564
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.156
Given I shutdown Tails and wait for the computer to power off 11.102
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:26.744
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 5.204
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.220
When the network is plugged 0.067
And Tor is ready 11.625
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.161
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 23.046
Given I shutdown Tails and wait for the computer to power off 13.980
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.437
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.939
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.058
And Tor is ready 16.708
Then the Upgrader considers the system as up-to-date 0.201
# 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.752
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.465
After features/support/hooks.rb:331 1.329
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
41.469
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.204
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 6.696
And Tor is ready 17.440
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.711
After features/support/hooks.rb:331 1.190
After features/support/hooks.rb:100 0.000