Project Number Date
test_Tails_ISO_stable 5692 02 Jun 2025, 13:19

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 21:59.242 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:48.440
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.238
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.071
And I write an old version of the Tails USB image to disk "old" 56.768
When I start Tails from USB drive "old" with network unplugged 1:45.782
Then the boot device has safe access rights 3.422
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.138
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:330 7.464
After features/support/hooks.rb:100 0.009
Tags: @product
2:19.324
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.263
And I start Tails from USB drive "old" with network unplugged and I login 1:29.208
Then Tails is running from USB drive "old" 0.554
And I create a persistent partition 35.942
And I take note of which tps features are available 3.389
Then a Tails persistence partition exists on USB drive "old" 0.885
And I shutdown Tails and wait for the computer to power off 9.080
After features/support/hooks.rb:330 0.194
After features/support/hooks.rb:100 0.011
Tags: @product
3:18.441
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.280
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.667
Then Tails is running from USB drive "old" 0.379
And all tps features are active 3.051
When I write some files expected to persist 2.128
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.310
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.782
And I take note of which tps features are available 4.582
And I shutdown Tails and wait for the computer to power off 6.650
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.149
After features/support/hooks.rb:330 0.099
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.338
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.073
And I log in to a new session 19.940
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.311
And I plug USB drive "to_upgrade" 2.693
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.268
Then the running Tails is installed on USB drive "to_upgrade" 26.579
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.250
After features/support/hooks.rb:330 6.774
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.186
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.266
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.965
Then all tps features from the old Tails version are active 2.022
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.494
And the expected persistent files created with the old Tails version are present in the filesystem 1.480
And all persistent directories from the old Tails version have safe access rights 2.599
After features/support/hooks.rb:330 1.634
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:5.433
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 16.227
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.536
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.440
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.081
And Tor is ready 22.138
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.118
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.638
Given I shutdown Tails and wait for the computer to power off 8.492
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.215
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 3.239
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.386
When the network is plugged 0.153
And Tor is ready 22.134
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.922
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.884
Given I shutdown Tails and wait for the computer to power off 4.336
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.282
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.098
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.088
And Tor is ready 18.485
Then the Upgrader considers the system as up-to-date 11.040
# 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 17.139
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.789
After features/support/hooks.rb:330 0.738
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
1:7.077
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 15.506
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
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.140
But a current signing key is available on our website 0.000
When the network is plugged 0.118
And Tor is ready 50.081
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.845
After features/support/hooks.rb:330 0.976
After features/support/hooks.rb:100 0.000