Project Number Date
test_Tails_ISO_stable 5994 09 Dec 2025, 15:13

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:2.312 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
2:5.314
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 40.346
When I start Tails from USB drive "old" with network unplugged 1:19.315
Then the boot device has safe access rights 3.488
And Tails is running from USB drive "old" 0.280
And there is no persistence partition on USB drive "old" 0.101
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.248
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:331 4.087
After features/support/hooks.rb:100 0.010
Tags: @product
2:2.875
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:26.694
Then Tails is running from USB drive "old" 0.296
And I create a persistent partition 29.105
And I take note of which tps features are available 1.055
Then a Tails persistence partition exists on USB drive "old" 0.663
And I shutdown Tails and wait for the computer to power off 4.884
After features/support/hooks.rb:331 0.647
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.056
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.620
Then Tails is running from USB drive "old" 0.334
And all tps features are active 1.882
When I write some files expected to persist 1.508
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.497
And all persistent directories from the old Tails version have safe access rights 2.541
And I take note of which tps features are available 0.477
And I shutdown Tails and wait for the computer to power off 7.538
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.236
After features/support/hooks.rb:331 0.413
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.684
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.798
And I log in to a new session 15.193
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.302
And I plug USB drive "to_upgrade" 2.577
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.099
Then the running Tails is installed on USB drive "to_upgrade" 21.236
And I unplug USB drive "to_upgrade" 0.254
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:331 3.802
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.235
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.751
Then all tps features from the old Tails version are active 1.647
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.248
And the expected persistent files created with the old Tails version are present in the filesystem 1.587
And all persistent directories from the old Tails version have safe access rights 2.482
After features/support/hooks.rb:331 0.651
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
4:21.346
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.728
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.402
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.581
When the network is plugged 0.060
And Tor is ready 15.892
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.984
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.146
Given I shutdown Tails and wait for the computer to power off 11.336
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.283
Then Tails is running version 6.2~testoverlayfs 0.033
And all tps features are active 2.202
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.191
# 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.268
When the network is plugged 0.055
And Tor is ready 11.048
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.900
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.246
Given I shutdown Tails and wait for the computer to power off 7.811
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.094
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.400
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.190
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.219
When the network is plugged 0.069
And Tor is ready 12.347
Then the Upgrader considers the system as up-to-date 0.130
# 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.857
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.506
After features/support/hooks.rb:331 0.817
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
24.799
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.959
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.116
And Tor is ready 11.339
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.872
After features/support/hooks.rb:331 1.109
After features/support/hooks.rb:100 0.000