Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 9 04 May 2026, 14:40

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:37.524 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:12.516
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.563
When I start Tails from USB drive "old" with network unplugged 54.145
Then the boot device has safe access rights 3.015
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:331 1.318
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.043
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 53.501
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 24.632
And I take note of which tps features are available 0.804
Then a Tails persistence partition exists on USB drive "old" 0.530
And I shutdown Tails and wait for the computer to power off 4.283
After features/support/hooks.rb:331 0.365
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.160
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.476
Then Tails is running from USB drive "old" 0.212
And all tps features are active 1.411
When I write some files expected to persist 1.471
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.529
And all persistent directories from the old Tails version have safe access rights 2.113
And I take note of which tps features are available 0.162
And I shutdown Tails and wait for the computer to power off 8.190
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.373
After features/support/hooks.rb:331 0.205
After features/support/hooks.rb:100 0.006
Tags: @product
2:13.463
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.794
And I log in to a new session 14.061
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.968
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.772
Then the running Tails is installed on USB drive "to_upgrade" 16.341
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 1.242
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.090
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.813
Then all tps features from the old Tails version are active 1.035
And Tails is running from USB drive "to_upgrade" 0.265
And the boot device has safe access rights 2.771
And the expected persistent files created with the old Tails version are present in the filesystem 1.228
And all persistent directories from the old Tails version have safe access rights 1.895
After features/support/hooks.rb:331 0.692
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:39.882
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.188
And no SquashFS delta is installed 0.078
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.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.408
When the network is plugged 0.017
And Tor is ready 23.527
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.399
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.386
Given I shutdown Tails and wait for the computer to power off 19.227
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.442
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.224
And the file system changes introduced in version 6.2~testoverlayfs are present 0.238
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.229
When the network is plugged 0.015
And Tor is ready 21.524
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.410
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.176
Given I shutdown Tails and wait for the computer to power off 17.427
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.716
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.179
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.261
When the network is plugged 0.018
And Tor is ready 20.728
Then the Upgrader considers the system as up-to-date 0.105
# 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.216
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.362
After features/support/hooks.rb:331 1.071
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
26.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.498
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 18.055
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.381
After features/support/hooks.rb:331 0.880
After features/support/hooks.rb:100 0.000