Project Number Date
test_Tails_ISO_devel 3860 10 Jun 2025, 13:40

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:32.397 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:6.986
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.256
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 31.759
When I start Tails from USB drive "old" with network unplugged 1:29.702
Then the boot device has safe access rights 3.171
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:330 6.993
After features/support/hooks.rb:100 0.012
Tags: @product
2:28.963
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:41.812
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 33.550
And I take note of which tps features are available 3.184
Then a Tails persistence partition exists on USB drive "old" 1.253
And I shutdown Tails and wait for the computer to power off 8.612
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.017
Tags: @product
2:56.755
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.743
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.639
Then Tails is running from USB drive "old" 0.386
And all tps features are active 1.908
When I write some files expected to persist 1.857
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.295
And all persistence configuration files have safe access rights 0.584
And all persistent directories from the old Tails version have safe access rights 2.639
And I take note of which tps features are available 0.680
And I shutdown Tails and wait for the computer to power off 4.542
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.477
After features/support/hooks.rb:330 0.120
After features/support/hooks.rb:100 0.013
Tags: @product
2:38.864
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.232
And I log in to a new session 19.677
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.908
And I plug USB drive "to_upgrade" 2.462
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.928
Then the running Tails is installed on USB drive "to_upgrade" 27.203
And I unplug USB drive "to_upgrade" 0.247
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 7.139
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.545
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.341
Then all tps features from the old Tails version are active 2.388
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.387
And the expected persistent files created with the old Tails version are present in the filesystem 2.259
And all persistent directories from the old Tails version have safe access rights 2.587
After features/support/hooks.rb:330 1.463
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:29.397
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 11.445
And no SquashFS delta is installed 0.167
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.595
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.534
When the network is plugged 0.091
And Tor is ready 22.873
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.466
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.754
Given I shutdown Tails and wait for the computer to power off 9.102
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.201
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.301
And the file system changes introduced in version 6.2~testoverlayfs are present 0.353
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.386
When the network is plugged 0.068
And Tor is ready 18.087
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.764
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.953
Given I shutdown Tails and wait for the computer to power off 1:0.061
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.827
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.127
And the file system changes introduced in version 6.3~testoverlayfs are present 0.614
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.082
And Tor is ready 18.444
Then the Upgrader considers the system as up-to-date 0.322
# 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.141
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.135
After features/support/hooks.rb:330 0.728
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
41.884
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.228
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.442
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
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.109
And Tor is ready 22.600
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.353
After features/support/hooks.rb:330 0.720
After features/support/hooks.rb:100 0.000