Project Number Date
test_Tails_ISO_devel 4093 29 Nov 2025, 15:15

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 16:56.836 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:57.804
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 32.208
When I start Tails from USB drive "old" with network unplugged 1:19.936
Then the boot device has safe access rights 3.282
And Tails is running from USB drive "old" 0.435
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.359
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:331 3.493
After features/support/hooks.rb:100 0.011
Tags: @product
2:8.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:27.809
Then Tails is running from USB drive "old" 1.073
And I create a persistent partition 29.401
And I take note of which tps features are available 1.301
Then a Tails persistence partition exists on USB drive "old" 0.723
And I shutdown Tails and wait for the computer to power off 7.818
After features/support/hooks.rb:331 0.285
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.499
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.307
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:38.908
Then Tails is running from USB drive "old" 0.908
And all tps features are active 2.412
When I write some files expected to persist 1.790
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 2.550
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 7.652
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.860
After features/support/hooks.rb:331 0.498
After features/support/hooks.rb:100 0.009
Tags: @product
2:43.326
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.230
And I log in to a new session 17.058
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.786
And I plug USB drive "to_upgrade" 2.695
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.238
Then the running Tails is installed on USB drive "to_upgrade" 22.880
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:331 3.773
After features/support/hooks.rb:100 0.000
Tags: @product
1:49.910
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:40.711
Then all tps features from the old Tails version are active 1.583
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.518
And the expected persistent files created with the old Tails version are present in the filesystem 1.479
And all persistent directories from the old Tails version have safe access rights 2.109
After features/support/hooks.rb:331 1.085
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:34.003
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 14.094
And no SquashFS delta is installed 0.154
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.490
When the network is plugged 0.074
And Tor is ready 15.718
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.963
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.104
Given I shutdown Tails and wait for the computer to power off 13.215
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.289
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.954
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.176
# 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.294
When the network is plugged 6.192
And Tor is ready 13.585
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.043
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.338
Given I shutdown Tails and wait for the computer to power off 7.945
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.563
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.259
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.161
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.049
And Tor is ready 11.218
Then the Upgrader considers the system as up-to-date 10.899
# 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.896
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 2.032
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
29.002
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 14.910
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 11.718
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.776
After features/support/hooks.rb:331 1.091
After features/support/hooks.rb:100 0.000