Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 4 23 Apr 2026, 14:42

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 12:3.764 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:11.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.105
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.083
When I start Tails from USB drive "old" with network unplugged 54.408
Then the boot device has safe access rights 2.651
And Tails is running from USB drive "old" 0.191
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.224
And I unplug USB drive "old" 0.161
After features/support/hooks.rb:331 3.637
After features/support/hooks.rb:100 0.030
Tags: @product
1:24.517
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 51.530
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 23.160
And I take note of which tps features are available 0.809
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.226
After features/support/hooks.rb:331 0.350
After features/support/hooks.rb:100 0.008
Tags: @product
1:22.122
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.434
Then Tails is running from USB drive "old" 0.236
And all tps features are active 1.062
When I write some files expected to persist 1.186
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.451
And all persistent directories from the old Tails version have safe access rights 1.801
And I take note of which tps features are available 0.141
And I shutdown Tails and wait for the computer to power off 7.917
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.663
After features/support/hooks.rb:331 0.174
After features/support/hooks.rb:100 0.006
Tags: @product
2:8.965
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.838
And I log in to a new session 11.105
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.772
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.614
Then the running Tails is installed on USB drive "to_upgrade" 15.081
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:331 2.057
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.072
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.375
Then all tps features from the old Tails version are active 1.020
And Tails is running from USB drive "to_upgrade" 0.266
And the boot device has safe access rights 2.488
And the expected persistent files created with the old Tails version are present in the filesystem 1.104
And all persistent directories from the old Tails version have safe access rights 1.770
After features/support/hooks.rb:331 0.614
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:26.112
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.023
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.252
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.331
When the network is plugged 0.016
And Tor is ready 22.242
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.410
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.089
Given I shutdown Tails and wait for the computer to power off 19.675
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.199
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.272
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.197
When the network is plugged 0.014
And Tor is ready 21.512
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.358
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.813
Given I shutdown Tails and wait for the computer to power off 13.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.032
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.129
And the file system changes introduced in version 6.3~testoverlayfs are present 0.348
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.171
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.014
And Tor is ready 20.899
Then the Upgrader considers the system as up-to-date 0.124
# 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.117
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.467
After features/support/hooks.rb:331 0.894
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
25.025
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.559
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 16.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.373
After features/support/hooks.rb:331 0.811
After features/support/hooks.rb:100 0.000