Project Number Date
test_Tails_ISO_devel 4096 01 Dec 2025, 22:27

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 15:53.937 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
1:49.990
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 33.014
When I start Tails from USB drive "old" with network unplugged 1:11.247
Then the boot device has safe access rights 3.411
And Tails is running from USB drive "old" 0.451
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.237
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:331 3.881
After features/support/hooks.rb:100 0.025
Tags: @product
2:10.303
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:27.345
Then Tails is running from USB drive "old" 0.613
And I create a persistent partition 31.709
And I take note of which tps features are available 1.650
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 7.993
After features/support/hooks.rb:331 0.225
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.853
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.772
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.961
When I write some files expected to persist 1.630
# 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.404
And all persistent directories from the old Tails version have safe access rights 2.869
And I take note of which tps features are available 0.519
And I shutdown Tails and wait for the computer to power off 8.326
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.636
After features/support/hooks.rb:331 0.146
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.854
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.518
And I log in to a new session 16.378
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.674
And I plug USB drive "to_upgrade" 4.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:58.308
Then the running Tails is installed on USB drive "to_upgrade" 22.103
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:331 3.934
After features/support/hooks.rb:100 0.000
Tags: @product
1:40.330
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:29.704
Then all tps features from the old Tails version are active 2.362
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.396
And the expected persistent files created with the old Tails version are present in the filesystem 1.726
And all persistent directories from the old Tails version have safe access rights 2.583
After features/support/hooks.rb:331 0.942
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:36.304
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.831
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.412
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.596
When the network is plugged 0.058
And Tor is ready 13.808
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.559
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.257
Given I shutdown Tails and wait for the computer to power off 13.462
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:29.347
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.074
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.113
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.183
# 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.228
When the network is plugged 0.077
And Tor is ready 12.391
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.683
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.892
Given I shutdown Tails and wait for the computer to power off 9.241
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.541
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 2.404
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.169
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.069
And Tor is ready 12.163
Then the Upgrader considers the system as up-to-date 0.329
# 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 6.216
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.559
After features/support/hooks.rb:331 1.127
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
25.302
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 with a persistent partition enabled and logged in 11.031
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 12.054
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.752
After features/support/hooks.rb:331 1.083
After features/support/hooks.rb:100 0.000