Project Number Date
test_Tails_ISO_stable 5488 03 Mar 2025, 21: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 19:54.139 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:13.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 33.695
When I start Tails from USB drive "old" with network unplugged 1:34.043
Then the boot device has safe access rights 3.128
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:330 3.544
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.452
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:30.040
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 33.485
And I take note of which tps features are available 1.587
Then a Tails persistence partition exists on USB drive "old" 0.902
And I shutdown Tails and wait for the computer to power off 8.880
After features/support/hooks.rb:330 0.378
After features/support/hooks.rb:100 0.013
Tags: @product
2:58.802
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.154
Then Tails is running from USB drive "old" 0.380
And all tps features are active 2.346
When I write some files expected to persist 1.786
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.278
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.725
And I take note of which tps features are available 0.420
And I shutdown Tails and wait for the computer to power off 4.564
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.519
After features/support/hooks.rb:330 0.128
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.105
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 11.402
And I log in to a new session 21.675
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.925
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.211
Then the running Tails is installed on USB drive "to_upgrade" 23.926
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.248
After features/support/hooks.rb:330 1.909
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.206
Then all tps features from the old Tails version are active 2.052
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.971
And the expected persistent files created with the old Tails version are present in the filesystem 1.681
And all persistent directories from the old Tails version have safe access rights 2.686
After features/support/hooks.rb:330 1.213
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
6:52.607
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 29.602
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.485
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.077
And Tor is ready 23.203
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.797
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.905
Given I shutdown Tails and wait for the computer to power off 8.644
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.189
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.127
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.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# 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.114
And Tor is ready 17.038
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.027
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.453
Given I shutdown Tails and wait for the computer to power off 4.500
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.593
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.163
And the file system changes introduced in version 6.3~testoverlayfs are present 0.543
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.393
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.322
When the network is plugged 0.069
And Tor is ready 18.300
Then the Upgrader considers the system as up-to-date 0.350
# 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 15.511
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.107
After features/support/hooks.rb:330 0.718
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.815
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 10.445
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.456
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.106
But a current signing key is available on our website 0.000
When the network is plugged 0.106
And Tor is ready 19.386
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.253
After features/support/hooks.rb:330 1.241
After features/support/hooks.rb:100 0.000