Project Number Date
test_Tails_ISO_stable 5637 09 May 2025, 08:58

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:52.877 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.865
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.477
When I start Tails from USB drive "old" with network unplugged 1:38.153
Then the boot device has safe access rights 2.933
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 7.124
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.252
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:32.800
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 31.433
And I take note of which tps features are available 2.507
Then a Tails persistence partition exists on USB drive "old" 0.742
And I shutdown Tails and wait for the computer to power off 8.252
After features/support/hooks.rb:330 0.188
After features/support/hooks.rb:100 0.008
Tags: @product
3:14.425
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:34.273
Then Tails is running from USB drive "old" 0.309
And all tps features are active 3.350
When I write some files expected to persist 1.848
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.466
And all persistent directories from the old Tails version have safe access rights 2.543
And I take note of which tps features are available 0.490
And I shutdown Tails and wait for the computer to power off 6.667
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.048
After features/support/hooks.rb:330 0.113
After features/support/hooks.rb:100 0.007
Tags: @product
2:28.393
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.596
And I log in to a new session 18.383
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.710
And I plug USB drive "to_upgrade" 2.614
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.601
Then the running Tails is installed on USB drive "to_upgrade" 21.092
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:330 2.073
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.185
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.722
Then all tps features from the old Tails version are active 1.702
And Tails is running from USB drive "to_upgrade" 0.421
And the boot device has safe access rights 3.936
And the expected persistent files created with the old Tails version are present in the filesystem 1.622
And all persistent directories from the old Tails version have safe access rights 2.570
After features/support/hooks.rb:330 1.970
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:39.593
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 11.756
And no SquashFS delta is installed 0.335
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.703
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.071
And Tor is ready 19.412
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.354
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.775
Given I shutdown Tails and wait for the computer to power off 8.636
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.089
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.509
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.398
# 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.256
When the network is plugged 0.088
And Tor is ready 19.070
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.668
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.014
Given I shutdown Tails and wait for the computer to power off 6.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.026
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.985
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
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.400
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.068
And Tor is ready 20.075
Then the Upgrader considers the system as up-to-date 0.304
# 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 16.486
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.637
After features/support/hooks.rb:330 0.655
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.161
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 9.392
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.647
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the signing key used by the Upgrader is outdated 0.111
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 19.216
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.628
After features/support/hooks.rb:330 0.701
After features/support/hooks.rb:100 0.000