Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 83 06 Jul 2026, 14: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 11:32.265 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:8.174
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.176
When I start Tails from USB drive "old" with network unplugged 50.605
Then the boot device has safe access rights 2.658
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.443
After features/support/hooks.rb:108 0.016
Tags: @product
1:29.771
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.044
And I start Tails from USB drive "old" with network unplugged and I login 51.806
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 24.518
And I take note of which tps features are available 4.477
Then a Tails persistence partition exists on USB drive "old" 0.502
And I shutdown Tails and wait for the computer to power off 8.186
After features/support/hooks.rb:339 0.556
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.471
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.026
Then Tails is running from USB drive "old" 0.249
And all tps features are active 4.805
When I write some files expected to persist 1.247
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 1.830
And I take note of which tps features are available 3.772
And I shutdown Tails and wait for the computer to power off 4.227
# 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" 11.665
After features/support/hooks.rb:339 0.367
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.868
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.986
And I log in to a new session 12.919
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.792
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.209
Then the running Tails is installed on USB drive "to_upgrade" 14.406
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.185
After features/support/hooks.rb:339 2.087
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.422
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.501
Then all tps features from the old Tails version are active 1.151
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.602
And the expected persistent files created with the old Tails version are present in the filesystem 1.060
And all persistent directories from the old Tails version have safe access rights 1.802
After features/support/hooks.rb:339 0.858
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:42.919
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.753
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.364
When the network is plugged 0.016
And Tor is ready 13.366
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.681
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.036
Given I shutdown Tails and wait for the computer to power off 5.453
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.742
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.702
And the file system changes introduced in version 6.2~testoverlayfs are present 0.267
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.200
When the network is plugged 0.020
And Tor is ready 11.343
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.520
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.157
Given I shutdown Tails and wait for the computer to power off 4.217
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.255
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.617
And the file system changes introduced in version 6.3~testoverlayfs are present 0.394
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.182
When the network is plugged 0.018
And Tor is ready 9.609
Then the Upgrader considers the system as up-to-date 10.524
# 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.135
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.379
After features/support/hooks.rb:339 0.993
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.636
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.145
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.044
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.067
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.065
After features/support/hooks.rb:339 0.534
After features/support/hooks.rb:108 0.000