Project Number Date
test_Tails_ISO_stable 5600 26 Apr 2025, 12: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 19:52.628 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:3.799
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.373
And I create a 7200 MiB disk named "old" 0.113
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 29.413
When I start Tails from USB drive "old" with network unplugged 1:28.446
Then the boot device has safe access rights 3.273
And Tails is running from USB drive "old" 0.379
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:330 3.779
After features/support/hooks.rb:100 0.011
Tags: @product
2:23.620
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:35.326
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 35.798
And I take note of which tps features are available 2.290
Then a Tails persistence partition exists on USB drive "old" 0.829
And I shutdown Tails and wait for the computer to power off 8.819
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.774
Then Tails is running from USB drive "old" 0.629
And all tps features are active 2.203
When I write some files expected to persist 2.278
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.412
And all persistent directories from the old Tails version have safe access rights 2.353
And I take note of which tps features are available 0.475
And I shutdown Tails and wait for the computer to power off 6.726
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.667
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.268
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 13.166
And I log in to a new session 19.338
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.750
And I plug USB drive "to_upgrade" 2.601
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.705
Then the running Tails is installed on USB drive "to_upgrade" 23.173
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.295
After features/support/hooks.rb:330 0.949
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.370
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.423
Then all tps features from the old Tails version are active 1.598
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.714
And the expected persistent files created with the old Tails version are present in the filesystem 1.664
And all persistent directories from the old Tails version have safe access rights 2.432
After features/support/hooks.rb:330 1.346
After features/support/hooks.rb:100 0.059
Tags: @product @automatic_upgrade
6:47.862
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 27.429
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.721
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.070
And Tor is ready 21.775
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.810
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.823
Given I shutdown Tails and wait for the computer to power off 8.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.540
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.278
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.242
When the network is plugged 0.067
And Tor is ready 17.104
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.982
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.360
Given I shutdown Tails and wait for the computer to power off 4.260
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.168
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.142
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.381
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.347
And Tor is ready 18.441
Then the Upgrader considers the system as up-to-date 0.314
# 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.497
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.045
After features/support/hooks.rb:330 0.753
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
36.774
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 10.230
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.514
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.108
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 17.364
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.388
After features/support/hooks.rb:330 0.657
After features/support/hooks.rb:100 0.000