Project Number Date
test_Tails_ISO_stable 5636 08 May 2025, 18:44

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 20:16.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:14.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.763
When I start Tails from USB drive "old" with network unplugged 1:37.069
Then the boot device has safe access rights 3.111
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:330 3.750
After features/support/hooks.rb:100 0.010
Tags: @product
2:18.483
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:33.474
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 32.639
And I take note of which tps features are available 2.577
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 8.419
After features/support/hooks.rb:330 0.181
After features/support/hooks.rb:100 0.012
Tags: @product
2:57.539
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.070
Then Tails is running from USB drive "old" 0.385
And all tps features are active 2.323
When I write some files expected to persist 1.909
# 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.427
And all persistent directories from the old Tails version have safe access rights 2.463
And I take note of which tps features are available 0.415
And I shutdown Tails and wait for the computer to power off 4.417
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.710
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.011
Tags: @product
2:37.597
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 without a persistent partition and stopped at Tails Greeter's login screen 10.470
And I log in to a new session 18.756
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.773
And I plug USB drive "to_upgrade" 2.530
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.869
Then the running Tails is installed on USB drive "to_upgrade" 24.751
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 3.306
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.367
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.288
Then all tps features from the old Tails version are active 1.633
And Tails is running from USB drive "to_upgrade" 0.384
And the boot device has safe access rights 3.694
And the expected persistent files created with the old Tails version are present in the filesystem 1.481
And all persistent directories from the old Tails version have safe access rights 2.653
After features/support/hooks.rb:330 1.092
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:6.070
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 13.647
And no SquashFS delta is installed 0.254
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.498
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.504
When the network is plugged 0.064
And Tor is ready 49.606
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.568
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.718
Given I shutdown Tails and wait for the computer to power off 13.138
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.050
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.235
And the file system changes introduced in version 6.2~testoverlayfs are present 0.404
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.381
When the network is plugged 0.066
And Tor is ready 19.876
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.562
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.697
Given I shutdown Tails and wait for the computer to power off 4.516
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.853
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.281
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.092
And Tor is ready 20.876
Then the Upgrader considers the system as up-to-date 0.335
# 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.690
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.172
After features/support/hooks.rb:330 0.975
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
42.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.181
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.109
And Tor is ready 22.647
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.927
After features/support/hooks.rb:330 0.999
After features/support/hooks.rb:100 0.000