Project Number Date
test_Tails_ISO_devel 3871 17 Jun 2025, 15:14

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 27:3.619 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:59.425
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.458
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 44.711
When I start Tails from USB drive "old" with network unplugged 2:2.652
Then the boot device has safe access rights 8.624
And Tails is running from USB drive "old" 0.653
And there is no persistence partition on USB drive "old" 0.111
And process "udev-watchdog" is running 0.144
And udev-watchdog is monitoring the correct device 0.751
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:330 4.077
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.019
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.307
And I start Tails from USB drive "old" with network unplugged and I login 1:50.148
Then Tails is running from USB drive "old" 0.721
And I create a persistent partition 44.163
And I take note of which tps features are available 2.594
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 12.282
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.014
Tags: @product
4:12.767
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:19.428
Then Tails is running from USB drive "old" 1.930
And all tps features are active 3.691
When I write some files expected to persist 1.823
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.761
And I take note of which tps features are available 0.765
And I shutdown Tails and wait for the computer to power off 7.290
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 34.191
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.022
Tags: @product
3:34.070
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.849
And I log in to a new session 24.991
And I clone USB drive "old" to a new USB drive "to_upgrade" 9.828
And I plug USB drive "to_upgrade" 3.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:7.177
Then the running Tails is installed on USB drive "to_upgrade" 31.372
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 7.163
After features/support/hooks.rb:100 0.000
Tags: @product
3:15.945
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.381
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:57.188
Then all tps features from the old Tails version are active 2.106
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 11.299
And the expected persistent files created with the old Tails version are present in the filesystem 1.671
And all persistent directories from the old Tails version have safe access rights 2.948
After features/support/hooks.rb:330 1.947
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
9:14.967
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.597
And no SquashFS delta is installed 0.183
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.637
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.653
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.601
When the network is plugged 0.101
And Tor is ready 30.312
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.771
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.322
Given I shutdown Tails and wait for the computer to power off 14.233
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:50.095
Then Tails is running version 6.2~testoverlayfs 0.105
And all tps features are active 5.344
And the file system changes introduced in version 6.2~testoverlayfs are present 1.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.404
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.466
# 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.524
When the network is plugged 0.263
And Tor is ready 24.777
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 12.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 18.377
Given I shutdown Tails and wait for the computer to power off 6.886
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:40.838
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 3.011
And the file system changes introduced in version 6.3~testoverlayfs are present 0.795
And only the 6.3~testoverlayfs SquashFS delta is installed 0.102
# 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.417
When the network is plugged 0.088
And Tor is ready 29.608
Then the Upgrader considers the system as up-to-date 0.428
# 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 23.146
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.827
After features/support/hooks.rb:330 0.739
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
55.422
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 15.477
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.672
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.133
And the signing key used by the Upgrader is outdated 0.191
But a current signing key is available on our website 0.000
When the network is plugged 0.148
And Tor is ready 26.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.799
After features/support/hooks.rb:330 2.008
After features/support/hooks.rb:100 0.000