Project Number Date
test_Tails_ISO_stable 5962 20 Nov 2025, 16:31

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:45.767 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:21.335
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 39.417
When I start Tails from USB drive "old" with network unplugged 1:36.691
Then the boot device has safe access rights 3.115
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.092
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:331 3.520
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.437
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:30.431
Then Tails is running from USB drive "old" 0.885
And I create a persistent partition 32.245
And I take note of which tps features are available 1.992
Then a Tails persistence partition exists on USB drive "old" 0.752
And I shutdown Tails and wait for the computer to power off 7.940
After features/support/hooks.rb:331 0.158
After features/support/hooks.rb:100 0.009
Tags: @product
2:19.832
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:44.472
Then Tails is running from USB drive "old" 0.355
And all tps features are active 2.078
When I write some files expected to persist 1.534
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.620
And all persistent directories from the old Tails version have safe access rights 2.637
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 8.036
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.236
After features/support/hooks.rb:331 0.108
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.925
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 without a persistent partition and stopped at Tails Greeter's login screen 18.171
And I log in to a new session 19.502
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.647
And I plug USB drive "to_upgrade" 2.588
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:55.687
Then the running Tails is installed on USB drive "to_upgrade" 21.914
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:331 7.909
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.658
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.162
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:40.756
Then all tps features from the old Tails version are active 2.083
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.431
And the expected persistent files created with the old Tails version are present in the filesystem 1.507
And all persistent directories from the old Tails version have safe access rights 2.411
After features/support/hooks.rb:331 0.851
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:34.640
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.451
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.550
When the network is plugged 0.073
And Tor is ready 43.996
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.763
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.595
Given I shutdown Tails and wait for the computer to power off 9.132
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.759
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.381
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.226
When the network is plugged 0.049
And Tor is ready 11.887
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.128
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.799
Given I shutdown Tails and wait for the computer to power off 3.154
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.783
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.232
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.197
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.221
When the network is plugged 0.058
And Tor is ready 17.972
Then the Upgrader considers the system as up-to-date 0.283
# 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 6.519
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.605
After features/support/hooks.rb:331 1.270
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
24.936
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 10.944
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 12.856
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.632
After features/support/hooks.rb:331 0.968
After features/support/hooks.rb:100 0.000