Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 3 22 Apr 2026, 14:55

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 13:19.065 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:17.709
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.937
When I start Tails from USB drive "old" with network unplugged 59.105
Then the boot device has safe access rights 2.794
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 1.408
After features/support/hooks.rb:100 0.006
Tags: @product
1:33.852
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 58.466
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 25.383
And I take note of which tps features are available 0.752
Then a Tails persistence partition exists on USB drive "old" 0.643
And I shutdown Tails and wait for the computer to power off 8.305
After features/support/hooks.rb:331 0.561
After features/support/hooks.rb:100 0.029
Tags: @product
1:23.088
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.351
Then Tails is running from USB drive "old" 0.281
And all tps features are active 1.199
When I write some files expected to persist 1.368
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.461
And all persistent directories from the old Tails version have safe access rights 2.089
And I take note of which tps features are available 0.280
And I shutdown Tails and wait for the computer to power off 2.884
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.924
After features/support/hooks.rb:331 0.271
After features/support/hooks.rb:100 0.007
Tags: @product
2:30.224
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 without a persistent partition and stopped at Tails Greeter's login screen 7.922
And I log in to a new session 18.367
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.937
And I plug USB drive "to_upgrade" 2.278
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.977
Then the running Tails is installed on USB drive "to_upgrade" 16.457
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:331 3.963
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.134
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.451
Then all tps features from the old Tails version are active 0.985
And Tails is running from USB drive "to_upgrade" 0.233
And the boot device has safe access rights 2.494
And the expected persistent files created with the old Tails version are present in the filesystem 1.081
And all persistent directories from the old Tails version have safe access rights 1.829
After features/support/hooks.rb:331 0.651
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:58.331
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 8.403
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
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.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.420
When the network is plugged 0.025
And Tor is ready 45.589
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.383
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.747
Given I shutdown Tails and wait for the computer to power off 20.103
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.403
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.023
And the file system changes introduced in version 6.2~testoverlayfs are present 0.213
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.187
When the network is plugged 0.015
And Tor is ready 21.527
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.377
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.329
Given I shutdown Tails and wait for the computer to power off 17.054
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.466
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.069
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.060
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.016
And Tor is ready 21.811
Then the Upgrader considers the system as up-to-date 0.101
# 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.166
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:331 0.615
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
27.723
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 7.420
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.099
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 19.552
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.358
After features/support/hooks.rb:331 1.212
After features/support/hooks.rb:100 0.000