Project Number Date
test_Tails_ISO_stable 5716 15 Jun 2025, 14:16

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:38.085 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:32.293
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.276
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 38.936
When I start Tails from USB drive "old" with network unplugged 1:45.922
Then the boot device has safe access rights 4.518
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.210
And udev-watchdog is monitoring the correct device 0.631
And I unplug USB drive "old" 0.256
After features/support/hooks.rb:330 4.356
After features/support/hooks.rb:100 0.011
Tags: @product
2:24.799
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login 1:36.615
Then Tails is running from USB drive "old" 0.524
And I create a persistent partition 35.648
And I take note of which tps features are available 2.668
Then a Tails persistence partition exists on USB drive "old" 0.832
And I shutdown Tails and wait for the computer to power off 8.244
After features/support/hooks.rb:330 0.146
After features/support/hooks.rb:100 0.010
Tags: @product
3:16.382
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.364
Then Tails is running from USB drive "old" 1.260
And all tps features are active 3.605
When I write some files expected to persist 2.536
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.598
And all persistent directories from the old Tails version have safe access rights 3.195
And I take note of which tps features are available 0.512
And I shutdown Tails and wait for the computer to power off 7.100
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.789
After features/support/hooks.rb:330 0.140
After features/support/hooks.rb:100 0.008
Tags: @product
2:44.820
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.305
And I log in to a new session 24.702
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.038
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.331
Then the running Tails is installed on USB drive "to_upgrade" 25.522
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 3.566
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.860
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.258
Then all tps features from the old Tails version are active 2.303
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 4.522
And the expected persistent files created with the old Tails version are present in the filesystem 1.969
And all persistent directories from the old Tails version have safe access rights 2.278
After features/support/hooks.rb:330 1.987
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:24.139
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 15.475
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.082
And Tor is ready 22.562
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.073
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.268
Given I shutdown Tails and wait for the computer to power off 12.959
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.526
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.281
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.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.250
When the network is plugged 0.071
And Tor is ready 20.509
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.148
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.003
Given I shutdown Tails and wait for the computer to power off 7.786
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.902
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.067
And the file system changes introduced in version 6.3~testoverlayfs are present 0.756
And only the 6.3~testoverlayfs SquashFS delta is installed 0.274
# 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.764
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.165
When the network is plugged 0.083
And Tor is ready 17.130
Then the Upgrader considers the system as up-to-date 0.340
# 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 18.069
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.660
After features/support/hooks.rb:330 1.983
After features/support/hooks.rb:100 0.062
Tags: @product @automatic_upgrade
41.790
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.898
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 21.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.169
After features/support/hooks.rb:330 0.874
After features/support/hooks.rb:100 0.000