Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 18 11 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 13:0.618 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.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.551
When I start Tails from USB drive "old" with network unplugged 58.343
Then the boot device has safe access rights 2.734
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.251
After features/support/hooks.rb:331 3.605
After features/support/hooks.rb:100 0.013
Tags: @product
1:35.361
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 58.528
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 26.467
And I take note of which tps features are available 0.942
Then a Tails persistence partition exists on USB drive "old" 0.618
And I shutdown Tails and wait for the computer to power off 8.470
After features/support/hooks.rb:331 0.526
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.156
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.121
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.117
Then Tails is running from USB drive "old" 0.277
And all tps features are active 1.588
When I write some files expected to persist 1.644
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.607
And all persistent directories from the old Tails version have safe access rights 2.209
And I take note of which tps features are available 0.198
And I shutdown Tails and wait for the computer to power off 6.948
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.225
After features/support/hooks.rb:331 0.196
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.742
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.195
And I log in to a new session 13.439
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.974
And I plug USB drive "to_upgrade" 2.251
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.520
Then the running Tails is installed on USB drive "to_upgrade" 17.030
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:331 2.258
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.439
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.121
Then all tps features from the old Tails version are active 1.001
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.595
And the expected persistent files created with the old Tails version are present in the filesystem 1.245
And all persistent directories from the old Tails version have safe access rights 2.165
After features/support/hooks.rb:331 1.020
After features/support/hooks.rb:100 0.006
4:42.098
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 8.794
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.037
And Tor is ready 23.222
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.388
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.618
Given I shutdown Tails and wait for the computer to power off 20.114
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.851
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.239
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.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.217
When the network is plugged 0.013
And Tor is ready 20.734
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.364
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.245
Given I shutdown Tails and wait for the computer to power off 13.621
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.980
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.177
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.019
And Tor is ready 21.784
Then the Upgrader considers the system as up-to-date 0.093
# 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.747
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.406
After features/support/hooks.rb:331 0.881
After features/support/hooks.rb:100 0.012
25.222
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.337
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
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.043
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 17.172
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.396
After features/support/hooks.rb:331 0.980
After features/support/hooks.rb:100 0.000