Project Number Date
test_Tails_ISO_stable 5972 27 Nov 2025, 14:41

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 17:10.656 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:7.689
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 34.676
When I start Tails from USB drive "old" with network unplugged 1:27.407
Then the boot device has safe access rights 3.280
And Tails is running from USB drive "old" 0.430
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.233
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:331 4.071
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.727
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:32.371
Then Tails is running from USB drive "old" 0.804
And I create a persistent partition 30.372
And I take note of which tps features are available 1.172
Then a Tails persistence partition exists on USB drive "old" 0.683
And I shutdown Tails and wait for the computer to power off 7.164
After features/support/hooks.rb:331 0.323
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.177
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.859
Then Tails is running from USB drive "old" 0.369
And all tps features are active 2.228
When I write some files expected to persist 1.734
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.503
And I take note of which tps features are available 0.670
And I shutdown Tails and wait for the computer to power off 7.800
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.127
After features/support/hooks.rb:331 0.301
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.399
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 without a persistent partition and stopped at Tails Greeter's login screen 13.943
And I log in to a new session 18.845
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.343
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.078
Then the running Tails is installed on USB drive "to_upgrade" 22.320
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.248
After features/support/hooks.rb:331 4.172
After features/support/hooks.rb:100 0.000
Tags: @product
1:54.640
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:44.873
Then all tps features from the old Tails version are active 1.735
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.306
And the expected persistent files created with the old Tails version are present in the filesystem 1.437
And all persistent directories from the old Tails version have safe access rights 2.757
After features/support/hooks.rb:331 0.949
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:22.658
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.778
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.537
When the network is plugged 0.082
And Tor is ready 14.526
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.691
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.648
Given I shutdown Tails and wait for the computer to power off 11.674
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.189
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.139
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
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.144
# 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.305
When the network is plugged 0.135
And Tor is ready 11.507
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.877
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.516
Given I shutdown Tails and wait for the computer to power off 8.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.800
Then Tails is running version 6.3~testoverlayfs 0.465
And all tps features are active 2.943
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
And only the 6.3~testoverlayfs SquashFS delta is installed 0.100
# 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.235
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.674
When the network is plugged 0.433
And Tor is ready 14.226
Then the Upgrader considers the system as up-to-date 0.267
# 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 8.074
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.595
After features/support/hooks.rb:331 2.083
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.364
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.235
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
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.064
And Tor is ready 16.255
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.355
After features/support/hooks.rb:331 1.859
After features/support/hooks.rb:100 0.000