Project Number Date
test_Tails_ISO_flatpak-whisperback 6 14 May 2026, 21:49

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 11:44.830 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:16.240
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.605
When I start Tails from USB drive "old" with network unplugged 57.144
Then the boot device has safe access rights 2.723
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:335 1.384
After features/support/hooks.rb:104 0.007
Tags: @product
1:32.916
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 57.380
Then Tails is running from USB drive "old" 0.219
And I create a persistent partition 26.279
And I take note of which tps features are available 0.517
Then a Tails persistence partition exists on USB drive "old" 0.647
And I shutdown Tails and wait for the computer to power off 7.822
After features/support/hooks.rb:335 0.477
After features/support/hooks.rb:104 0.007
Tags: @product
1:26.495
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.868
Then Tails is running from USB drive "old" 0.255
And all tps features are active 1.192
When I write some files expected to persist 1.339
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.307
And all persistent directories from the old Tails version have safe access rights 2.116
And I take note of which tps features are available 0.167
And I shutdown Tails and wait for the computer to power off 4.167
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.813
After features/support/hooks.rb:335 0.335
After features/support/hooks.rb:104 0.006
Tags: @product
2:12.316
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.306
And I log in to a new session 12.878
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.829
And I plug USB drive "to_upgrade" 2.288
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.862
Then the running Tails is installed on USB drive "to_upgrade" 15.792
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:335 2.363
After features/support/hooks.rb:104 0.000
Tags: @product
1:15.659
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.428
Then all tps features from the old Tails version are active 1.224
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 2.942
And the expected persistent files created with the old Tails version are present in the filesystem 1.454
And all persistent directories from the old Tails version have safe access rights 2.248
After features/support/hooks.rb:335 0.747
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:41.861
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.732
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.359
When the network is plugged 0.015
And Tor is ready 13.930
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.663
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.731
Given I shutdown Tails and wait for the computer to power off 7.219
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.463
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.220
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.202
When the network is plugged 0.012
And Tor is ready 11.727
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.325
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.367
Given I shutdown Tails and wait for the computer to power off 4.052
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.892
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.389
And the file system changes introduced in version 6.3~testoverlayfs are present 0.337
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.188
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.238
When the network is plugged 0.015
And Tor is ready 9.987
Then the Upgrader considers the system as up-to-date 10.535
# 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 4.733
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.407
After features/support/hooks.rb:335 1.120
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
19.340
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.577
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.612
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.808
After features/support/hooks.rb:335 0.900
After features/support/hooks.rb:104 0.000