Project Number Date
test_Tails_ISO_devel 3809 13 May 2025, 20:24

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 21:34.633 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
3:23.894
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.314
And I create a 7200 MiB disk named "old" 0.081
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 1:8.268
When I start Tails from USB drive "old" with network unplugged 2:9.517
Then the boot device has safe access rights 3.606
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 7.376
After features/support/hooks.rb:100 0.013
Tags: @product
2:26.530
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.996
And I start Tails from USB drive "old" with network unplugged and I login 1:38.842
Then Tails is running from USB drive "old" 0.399
And I create a persistent partition 33.705
And I take note of which tps features are available 2.345
Then a Tails persistence partition exists on USB drive "old" 0.960
And I shutdown Tails and wait for the computer to power off 9.280
After features/support/hooks.rb:330 0.244
After features/support/hooks.rb:100 0.013
Tags: @product
3:13.858
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.885
Then Tails is running from USB drive "old" 0.762
And all tps features are active 2.598
When I write some files expected to persist 2.349
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.521
And all persistent directories from the old Tails version have safe access rights 3.065
And I take note of which tps features are available 1.155
And I shutdown Tails and wait for the computer to power off 6.634
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.399
After features/support/hooks.rb:330 0.174
After features/support/hooks.rb:100 0.011
Tags: @product
2:46.433
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.010
And I log in to a new session 21.204
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.051
And I plug USB drive "to_upgrade" 2.678
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.322
Then the running Tails is installed on USB drive "to_upgrade" 28.690
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.249
After features/support/hooks.rb:330 2.742
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.332
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.236
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.572
Then all tps features from the old Tails version are active 2.231
And Tails is running from USB drive "to_upgrade" 0.404
And the boot device has safe access rights 3.239
And the expected persistent files created with the old Tails version are present in the filesystem 1.359
And all persistent directories from the old Tails version have safe access rights 2.287
After features/support/hooks.rb:330 1.648
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
6:37.981
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.137
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.843
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.070
And Tor is ready 24.124
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.108
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.099
Given I shutdown Tails and wait for the computer to power off 8.779
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.990
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.415
And the file system changes introduced in version 6.2~testoverlayfs are present 0.407
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.344
# 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.293
When the network is plugged 0.070
And Tor is ready 20.344
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.474
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.807
Given I shutdown Tails and wait for the computer to power off 4.342
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.065
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.019
And the file system changes introduced in version 6.3~testoverlayfs are present 1.280
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.326
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.078
And Tor is ready 18.581
Then the Upgrader considers the system as up-to-date 0.343
# 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.498
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.650
After features/support/hooks.rb:330 0.690
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
41.602
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.283
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.100
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.125
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 21.798
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.119
After features/support/hooks.rb:330 0.692
After features/support/hooks.rb:100 0.000