Project Number Date
test_Tails_ISO_stable 5683 28 May 2025, 16:48

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:11.435 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:33.444
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.252
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.072
And I write an old version of the Tails USB image to disk "old" 30.961
When I start Tails from USB drive "old" with network unplugged 1:56.890
Then the boot device has safe access rights 3.131
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:330 7.404
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.829
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.296
And I start Tails from USB drive "old" with network unplugged and I login 1:27.533
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 32.125
And I take note of which tps features are available 1.740
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.946
After features/support/hooks.rb:330 0.166
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.436
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.383
Then Tails is running from USB drive "old" 0.413
And all tps features are active 2.049
When I write some files expected to persist 2.133
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.587
And I take note of which tps features are available 0.553
And I shutdown Tails and wait for the computer to power off 4.460
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.947
After features/support/hooks.rb:330 0.110
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.020
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 11.676
And I log in to a new session 20.080
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.775
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.461
Then the running Tails is installed on USB drive "to_upgrade" 24.122
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 3.543
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.754
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.935
Then all tps features from the old Tails version are active 1.842
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 3.486
And the expected persistent files created with the old Tails version are present in the filesystem 1.439
And all persistent directories from the old Tails version have safe access rights 2.511
After features/support/hooks.rb:330 1.105
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:58.233
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 12.674
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.618
When the network is plugged 0.121
And Tor is ready 26.197
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.364
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.396
Given I shutdown Tails and wait for the computer to power off 11.755
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.313
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.618
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.636
# 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.402
When the network is plugged 0.088
And Tor is ready 17.889
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.059
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.085
Given I shutdown Tails and wait for the computer to power off 7.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.064
Then Tails is running version 6.3~testoverlayfs 0.041
And all tps features are active 2.176
And the file system changes introduced in version 6.3~testoverlayfs are present 0.575
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.448
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.427
When the network is plugged 0.090
And Tor is ready 17.637
Then the Upgrader considers the system as up-to-date 0.337
# 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.619
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.814
After features/support/hooks.rb:330 0.794
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
42.716
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.319
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.393
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.248
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.111
And Tor is ready 21.590
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.978
After features/support/hooks.rb:330 3.687
After features/support/hooks.rb:100 0.000